This repository has been archived by the owner on Jan 13, 2025. It is now read-only.
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.
Problem
A Push Fanout of 6 is too small, resulting in the following:
The key here is that by increasing push fanout, gossip is able to reach more nodes in fewer hops. The pruning logic then removes the redundant paths, leaving us with a more dense MST without significant overhead (in steady state).
All numbers and claims below are based off of a simulated gossip framework here: gossip-sim
Data from simulated gossip framework can be found here: Grafana Dashboard
Summary of Changes
CRDS_GOSSIP_PUSH_FANOUT
from 6 to 9, while leavingCRDS_GOSSIP_PUSH_ACTIVE_SET_SIZE
at 12Supporting Data
Increasing Push Fanout from 6 to 9:
Pros
Cons
Fixes #