waku-org
/
test-waku-query
mirror of https://github.com/waku-org/test-waku-query.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
22 Commits 12 Branches 0 Tags 710 KiB
Go 51.4%
Shell 46.6%
Dockerfile 1.7%
Makefile 0.3%
Go to file
Ivan Folgueira Bande 1002b6ebb4 docker-compose.yml 
Uncommenting publisher container.
Exposing ports outside the containers.
Upgrading pending containers to nwaku version 0.20.0.
 		2023-10-23 22:43:21 +02:00
docker docker-compose.yml 2023-10-23 22:43:21 +02:00
go go/main_test.go: adding new test to compare databases performance 2023-10-15 20:28:11 +02:00
sh sh/publish_one_client.sh: adding content topic 2023-10-15 20:28:11 +02:00
.gitignore adding a Docker compose option that allows to compare postgres & sqlite metrics 2023-08-24 19:25:29 +02:00
README.md Including jmeter to allow concurrent Store requests easily 2023-09-05 14:44:57 +02:00

README.md

Summary

This repo contains tools for analysing performance around the Store protocol

Golang tool

The Golang project is aimed to setup go-waku clients that publish messages and later make requests trough the Store protocol to retrieve the stored messages

To run the tests, go to the go folder and run the make command. Notice that the go tool expects a running nwaku node(s) to be running with Store protocol mounted, and a running postgres database.

Bash tool

Simple script that allows to publish messages from different clients.

BASH(n clients) --json-rpc--> nwaku_A <--relay--> nwaku_B <---> database

Notice that the bash script expects two nwaku nodes that communicate through the Relay protocol and the nwaku_B has the Store protocol mounted and is connected to the postgres_DB.

Docker

Contains a docker compose file with:

  • Two nwaku nodes configured with Postgres and SQLite.
  • Grafana container to compare performance of both nodes.
  • Container with simple shell script that sends publish requests through rpc.
  • Two nwaku nodes configured as Store-clients and listening to REST requests.

Inside the docker folder, we have a jmeter test plan which is aimed for performing concurrent Store REST requests to the Store-clients.