209913ed4f
The latest image, 1b7c16, introduces the following: Passing peers as a list and using pubsubTopic & contentTopic params This commit represents changes on how the parameters are handled. There are many automatic/formatic changes made by the IDE. The major changes are: - The user can pass a comma-separated list of peers (peer-store-sqlite-addr-list and peer-store-postgres-addr-list.) - The pubsubTopic and contentTopic, which are part of the Store request, can be passed as a parameters as well. |
||
---|---|---|
.. | ||
imgs | ||
jmeter | ||
monitoring | ||
postgres_cfg | ||
README.md | ||
docker-compose-manual-binaries.yml | ||
msg_publisher.sh | ||
run_bootstrap.sh | ||
run_database_hammer.sh | ||
run_nwaku_store_postgres_ubuntu.sh | ||
run_nwaku_store_sqlite_ubuntu.sh | ||
run_waku_store_query_maker.sh | ||
run_wakupublisher.sh |
README.md
Summary
The docker compose starts two nwaku nodes with the Store protocol mounted but one is connected to SQLite and the other to Postgres. The performance can be compared through grafana.
Details
The two nodes are interconnected.
Grafana dashboard helps to compare performance
Within the docker compose we define another entities that make the nwaku nodes to send messages between them, and therefore, each received message is stored. On the other hand, another container(s) perform Store requests.