Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gossipsub scoring improvements #2391

Merged
merged 6 commits into from
Jul 13, 2021
Merged

Gossipsub scoring improvements #2391

merged 6 commits into from
Jul 13, 2021

Conversation

AgeManning
Copy link
Member

Gossipsub scoring is currently having issues on mainnet and the testnets.

From some inspection the causes seem to be:

  • Go gossipsub are packing more messages into RPC responses and for security limits we are limiting responses to 10 (some can gave > 200). I've changed this setting to allow up to 500 messages per RPC.
  • There are a number of nodes under the same IP. We currently only permit 3 nodes per IP before that start being scored down. The network is showing 5 or 6 peers on the same IP. I've increased this to 8.
  • On prater with lots of validators, messages are not being forward because we can't validate them in the time that we keep them around in the cache. The cache currently exists for 2.1 seconds, I've increased this to 8.4 seconds (will use more RAM however).

@AgeManning AgeManning merged commit 9e73bd0 into network-1.5 Jul 13, 2021
@AgeManning AgeManning deleted the gossipsub-scoring branch July 13, 2021 05:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v1.5.0 For inclusion in v1.5.0 release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant