Isolated traffic - request to join
[TODO: Add link to python script]
| msgs/s | Nº messages | relay nodes | light nodes | service nodes |
|---|---|---|---|---|
| 1 | - | 22 | - | 1 |
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 nodes. This is explained in Subscription Performance.
In this scenario, the results will be much more meaningful if we increase the total number of nodes, making nodes communication much higher, easier detecting if there is a minimum impact.
Nodes that are in relay-1 are nodes that are part of the same community. Nodes in relay-2 are not joined to any community.
✅ Experiment 1: Bandwidth usage on request to join community traffic doesn't affect nodes that are not in the community.
✅ Experiment 2: Bandwidth usage on request to join community traffic doesn't affect nodes that are not in the community.
✅ Experiment 3: Bandwidth usage on request to join community traffic doesn't affect nodes that are not in the community.
✅ Experiment 4: Bandwidth usage on request to join community traffic doesn't affect nodes that are not in the community.
✅ Experiment 5: Bandwidth usage on request to join community traffic doesn't affect nodes that are not in the community.
Comparison of received idle bandwidth from the entire container on 5 different experiments, community vs non community.
Comparison of sent idle bandwidth from the entire container on 5 different experiments, community vs non community.