Subscription performance

[TODO: Add link to python script]

msgs/s Nº messages relay nodes light nodes service nodes
1 180 10 40 5

This setup was run 5 times to obtain enough data to not get biased by one result. We didn’t run the numbers mentioned in the task description because of a problem we faced with increasing the number of light nodes. This is explained below.

Results will be averaged when doing the final comparison with nWaku, making the comparison with only a single box plot easier to analyze.

The average times from light nodes to start receiving messages after login on each experiment are:

Experiment 1 21.575 seconds
Experiment 2 20.9 seconds
Experiment 3 20.35 seconds
Experiment 4 18.3 seconds
Experiment 5 23.95 seconds

This is the information that can be also seen in the following figure:


<aside> 💡

When increasing the number of light nodes, we discovered an increasing time in receiving messages after login:

Nº Light nodes delay
40 20.9 seconds
40 19.1 seconds
50 26.34 seconds
60 38.6 seconds
70 33 seconds
80 50 seconds
</aside>

Message delays:

Time to readiness to receive live messages in 5 repeated scenarios.

Time to readiness to receive live messages in 5 repeated scenarios.

Bandwidth usage:

Comparison of received bandwidth from the entire container on 5 different experiments, relay vs light.

Comparison of received bandwidth from the entire container on 5 different experiments, relay vs light.

Comparison of sent bandwidth from the entire container on 5 different experiments, relay vs light.

Comparison of sent bandwidth from the entire container on 5 different experiments, relay vs light.

Memory usage:

Comparison of RAM usage from the entire container on 5 different experiments, relay vs light.

Comparison of RAM usage from the entire container on 5 different experiments, relay vs light.