Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Add P2P QA test case to check block, transaction and signature message rebound count #3952

Closed
jondubois opened this issue Jul 12, 2019 · 0 comments

Comments

@jondubois
Copy link
Contributor

jondubois commented Jul 12, 2019

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants