-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
rolls out merkle shreds to 100% of testnet slots #32316
rolls out merkle shreds to 100% of testnet slots #32316
Conversation
796ff1b
to
7fcaca7
Compare
Codecov Report
@@ Coverage Diff @@
## master #32316 +/- ##
=======================================
Coverage 82.0% 82.0%
=======================================
Files 773 773
Lines 209659 209659
=======================================
+ Hits 172097 172108 +11
+ Misses 37562 37551 -11 |
So kind of eye-balling it from your post in #31950 (comment), it seems as if:
|
Don't know how to interpret that. But since overall repair numbers are pretty low, and worst slots/nodes have improved, I feel ok with that. |
Might have abused some terminology, but as a concrete example:
The "best" 75% of nodes do better with legacy, but the entire cluster (or 99% of it that are reporting metrics) do better with merkle. So, a bigger spread for legacy.
True - I'm probably guilty of splitting hairs here by comparins |
(cherry picked from commit b722ce4)
…32316) (#32336) rolls out merkle shreds to 100% of testnet slots (#32316) (cherry picked from commit b722ce4) Co-authored-by: behzad nouri <[email protected]>
Problem
Ramping up Merkle shreds rollout as the results look good: #31950 (comment)
Summary of Changes
Rolls out merkle shreds to 100% of testnet slots.