test-waku-query

History

Ivan Folgueira Bande fd1f70610d max-connections=2 in both sqlite and postgres nodes		2023-11-07 12:57:20 +01:00
..
imgs	adding a Docker compose option that allows to compare postgres & sqlite metrics	2023-08-24 19:25:29 +02:00
jmeter	Moving jmeter related files to a jmeter folder	2023-11-07 12:57:20 +01:00
monitoring	Connecting nodes with bootstrap node and adding go-waku store clients	2023-10-23 22:43:21 +02:00
postgres_cfg	postgres.conf for 2GB RAM and 1 core	2023-10-23 22:43:21 +02:00
README.md	adding a Docker compose option that allows to compare postgres & sqlite metrics	2023-08-24 19:25:29 +02:00
docker-compose-manual-binaries.yml	Stop using the "replica" concept from docker-compose-manual-binaries	2023-11-07 12:57:20 +01:00
msg_publisher.sh	docker/msg_publisher.sh: setting a more realisting message size	2023-10-15 20:28:11 +02:00
run_bootstrap.sh	run_bootstrap: adding status.prod dns-discovery-url	2023-11-07 12:57:20 +01:00
run_nwaku_store_postgres_ubuntu.sh	max-connections=2 in both sqlite and postgres nodes	2023-11-07 12:57:20 +01:00
run_nwaku_store_sqlite_ubuntu.sh	max-connections=2 in both sqlite and postgres nodes	2023-11-07 12:57:20 +01:00
run_waku_store_query_maker.sh	docker-compose-manual: set num users store_query_maker from env	2023-11-07 12:57:20 +01:00
run_wakupublisher.sh	Connecting nodes with bootstrap node and adding go-waku store clients	2023-10-23 22:43:21 +02:00

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.