You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current efforts of testing long-term usage of js-waku required manually running an example and observing it. We should move towards a more automated solution. Additionally, it's important to gather metrics for how js-waku behaves in realistic conditions, across many browsers and locations.
Proposed Solutions
Create a webapp that runs a waku node and sends/listens to sequences of messages. Every time a message is successfully sent or received, it sends a request to the telemetry service with relevant metrics along with a wallet address.
To complete sequences:
generate random number and hash it
randomly pick a number of total messages in the sequence, between 5 and 20
randomly pick how often to send each message, between 1 and 3 seconds
send structured messages starting with index 0 to the total number using light push
each time a message is successfully sent to at least one peer, push the information to the telemetry service
Similarly, listen for messages using filter and push information to the telemetry service whenever one is decoded and received.
This is a feature request
Problem
Current efforts of testing long-term usage of js-waku required manually running an example and observing it. We should move towards a more automated solution. Additionally, it's important to gather metrics for how js-waku behaves in realistic conditions, across many browsers and locations.
Proposed Solutions
Create a webapp that runs a waku node and sends/listens to sequences of messages. Every time a message is successfully sent or received, it sends a request to the telemetry service with relevant metrics along with a wallet address.
To complete sequences:
Similarly, listen for messages using filter and push information to the telemetry service whenever one is decoded and received.
Notes
The text was updated successfully, but these errors were encountered: