vac:dst:deployment-and-analysis:waku:midscale §
%%{
init: {
@@ -21,7 +21,7 @@ gantt
Midscale: 2024-05-01, 2024-11-01
-- status: 20%
+- status: 40%
- CC: Wings
Description §
@@ -38,15 +38,21 @@ gantt
If nodes go online/offline, we should be able to retrieve missing messages from the store. This will also test Waku message relaying in a different way.
-- Filter and lightpush tests
- Measure (1) and (3) in heterogenous clusters involving different node implementations such as nwaku and go-waku
+- Test waku shard behaviour and stability with various of numbers of shards
+- Filter and lightpush tests
- Measure (3) with Waku peer exchange protocol used for discovery by a subset of nodes.
- Measure (1) with a mix of nodes using Resource-restricted device reliability protocol and peer exchange, meaning a small number of nwaku nodes serve store, light push and filter protocols and a high number of clients consume them. For example, 6-10 service nodes, 200 relay nodes and 1000 light nodes.
This should include connection and node churn impact on reliability for both relay and light clients.
+Additionally, perform monthly regression tests against a chosen version of Waku to ensure that no new bugs have been introduced. Produce a report on the results of the tests and any interesting findings.
Justification §
+Provide a greater understanding of Waku’s performance and reliability in midsized networks.
Deliverables §
-Similar deliverables to 10k sim, but with focuses on smaller scale and more frequent deployments.