-
-
Notifications
You must be signed in to change notification settings - Fork 299
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: update beacon max-old-space-size to 8192 #6343
Conversation
|
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## unstable #6343 +/- ##
=========================================
Coverage 60.13% 60.13%
=========================================
Files 407 407
Lines 46451 46451
Branches 1534 1534
=========================================
Hits 27935 27935
Misses 18486 18486
Partials 30 30 |
65c1b9e
to
ff115ad
Compare
Performance Report✔️ no performance regression detected Full benchmark results
|
🎉 This PR is included in v1.15.0 🎉 |
Motivation
--max-old-space-size
#6137Description
As discussed in the standup, we should increase our default heap memory limit. In the issue I initially proposed to use 6GB but from the call today it sounded like the consensus is rather to increase it to 8GB to prevent the node from crashing during non-finality or even potential DDoS attacks.
The downside of increasing the limit might be a slightly higher memory usage but it is not really clear how much impact this has. Increasing the limit might even be helpful to reduce GC overhead as the node should be consistently below the set limit now, even on Holesky.
This value can be revisited once #5968 is fully implemented and we are able to handle bad network conditions like non-finality without having a huge increase in memory.
Note: I did not update all occurrences of
--max-old-space-size
that we have in the code base as I think it is either not required or might be helpful if we get an error due to reaching the limit there.Closes #6137