New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create Waku diagnostic tool #308

Open

felicio opened this issue Sep 6, 2022 · 2 comments

Collaborator

felicio commented Sep 6, 2022 •

edited

Loading

What

Test
- The difference in perf. between the fleets/networks that are bridged to waku v1 and the fleets/networks that are not
  and
- The differences in perf. between the nim-waku fleets and go-waku fleets
- Spec source https://discord.com/channels/624205794384281629/1014557341926043769/1015208208249409586

Collaborator Author

felicio commented Sep 6, 2022 •

edited

Loading

My notes:

for protocol type
- fetching / store
- observing / relay
ops
- type
  - connecting
  - en/decoding
  - waiting
- fields
  - start time / crated at
  - end time / received at
query params
- topic
- direction
- size
- start time
- end time
request fields
- fleet
- node/peer address
response fields
- message id(s)
- message count
- call count
test fields
- start time
- end time
- elapsed time
message type
- community
- chat message
misc.
- earch record/test run per line
kibana link
grafana link
versions / commit
- js-waku
- status-web
- nim-waku
- go-waku
?from diff locations (e.g. us, eu)

?run test periodically in a headless browser deployed to a server and send results to elastic

Collaborator Author

felicio commented Sep 20, 2022

Relates to waku-org/nwaku#1160

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment