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
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
There needs to be a QA test case to check how many times a message bounces back to a node due to propagation.
Each node should only propagate blocks, transactions and signatures which they haven't already processed. Now that the 2.3 network is a partial mesh, we should be getting fewer rebound messages than we did in previous versions (which formed a full mesh network). Knowing this metric should help us to better evaluate future implementations which affect the bandwidth consumption of the network.
Actual behavior
There are no test cases to measure the average rebound rate of messages (for each node) as part of QA.
Which version(s) does this affect? (Environment, OS, etc...)
2.3
The text was updated successfully, but these errors were encountered:
Expected behavior
There needs to be a QA test case to check how many times a message bounces back to a node due to propagation.
Each node should only propagate blocks, transactions and signatures which they haven't already processed. Now that the 2.3 network is a partial mesh, we should be getting fewer rebound messages than we did in previous versions (which formed a full mesh network). Knowing this metric should help us to better evaluate future implementations which affect the bandwidth consumption of the network.
Actual behavior
There are no test cases to measure the average rebound rate of messages (for each node) as part of QA.
Which version(s) does this affect? (Environment, OS, etc...)
2.3
The text was updated successfully, but these errors were encountered: