mixclient: Introduce random message jitter #3388
Merged
+237
−63
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this change, random per-peer (per-identity) and per-message jitter are added to add additional delay to all message broadcasts. The jitter delay will range from 0-3s, with a random 0-2700ms of that being per-peer and 0-300ms being per-message. The total delay is calculated as 1/10 of the stage timeout duration, and the per-message delay is calculated is both the mean and median of dcrd's inventory trickling delay.
While here, pair request messages are also submitted to the network with random delays spanning over the entire epoch duration, while avoiding any PR sends during the 30s before and after the epoch.