-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
fix: adjust n-historical-states param #7104
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## unstable #7104 +/- ##
============================================
+ Coverage 48.94% 48.95% +0.01%
============================================
Files 597 597
Lines 39803 39833 +30
Branches 2065 2065
============================================
+ Hits 19481 19502 +21
- Misses 20280 20290 +10
+ Partials 42 41 -1 |
Performance Report✔️ no performance regression detected 🚀🚀 Significant benchmark improvement detected
Full benchmark results
|
blocked by #7109 |
a3d0117
to
296ba0e
Compare
as discussed in team's meeting, I enabled
with the modified default params in this PR:
|
* fix: default params of n-historical-states config * chore: improve log * feat: enable nHistoricalStates by default * chore: fix typo in log
Motivation
In holesky, lodestar had to reload and regen state for a weird orphaned block
this happens on a n-historical states node
Description
DEFAULT_MAX_BLOCK_STATES
to 64, this guarantees we don't have to reload state due to gossip blockDEFAULT_MAX_CP_STATE_EPOCHS_IN_MEMORY
to 3.