Tighten the minimal streams per 100ms for staked node #737
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The small staked's minimal streams per second is too generous. The one barely be entitled to 10 PPS can get 80 making it effective in QOS.
Summary of Changes
This change achieve the following results which matches master's behavior
1, On the tpu forward port where unstaked connections is 0, set the staked node's minimal PPS to 10 instead of 80
2. On the tpu port, set the staked nodes's minimal streams per 100MS to the the one of unstaked connection's + 1 in 100MS. This encourage more staked vs unstaked.
Fixes #