We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
#2373
Based on previous Turbine fanout experiment, larger fanouts are more effective in propagating shreds and reducing repairs: https://discord.com/channels/428295358100013066/478692221441409024/1265782094211321897
However the optimal fanout value cannot be inferred from the experiment.
In order to identify optimal fanout value, this commit extends the experiment with wider fanout values.
BZn14Liea52wtBwrXUxTv6vojuTTmfc7XGEDTXrvMD7b
Single Core Contributor
v2.0.10
v1.18.24
No response
The text was updated successfully, but these errors were encountered:
Replacing this with: https://github.com/orgs/anza-xyz/projects/9/views/1?pane=issue&itemId=86808518&issue=anza-xyz%7Cfeature-gate-tracker%7C63
Creating the feature gates in the anza-xyz/feature-gate-tracker makes labels accessible and keeps permissions consistent
Sorry, something went wrong.
behzadnouri
No branches or pull requests
SIMD
Description
#2373
Based on previous Turbine fanout experiment, larger fanouts are more effective in propagating shreds and reducing repairs: https://discord.com/channels/428295358100013066/478692221441409024/1265782094211321897
However the optimal fanout value cannot be inferred from the experiment.
In order to identify optimal fanout value, this commit extends the experiment with wider fanout values.
Feature ID
BZn14Liea52wtBwrXUxTv6vojuTTmfc7XGEDTXrvMD7b
Activation Method
Single Core Contributor
Deployment Considerations
Minimum Beta Version
v2.0.10
Minimum Stable Version
v1.18.24
Testnet Activation Epoch
No response
Devnet Activation Epoch
No response
Mainnet-Beta Activation Epoch
No response
The text was updated successfully, but these errors were encountered: