-
Notifications
You must be signed in to change notification settings - Fork 679
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
Memory usage increases significantly during non-finality #1795
Comments
Yes! Both 0.3.1 and 0.3.2 should be a lot gentler on RAM. I think around 5.5GB should be the highest it gets to now |
Closing this since reducing memory usage during non-finality is a well-known issue and this issue doesn't identify and specific bug we need to fix. Thanks for raising it and providing detail :) |
I am currently syncing Medalla with lighthouse and seeing absolutely insane memory consumption -- currently at almost 40 GB. This morning it locked up my 64 GB machine, and I had to reboot. |
|
Description
Lighthouse hit a peak of 10.09 GiB of RAM usage during the recent non-finality period on Medalla
Version
I was on v0.2.12 (via dappnode package) when I hit 10.09 GiB though I have since upgraded to v0.2.13-c0e76d2 (again via dappnode) and usage is again rising rapidly on a similar looking curve (originally it took ~5 days to reach the peak)
Present Behaviour
RAM consumption rises significantly while the chain is failing to finalize, easily exceeding the amounts of RAM that are recommended in most guides for running beacon nodes. Obviously could be related to #1782
Expected Behaviour
RAM consumption should remain within the recommended specs unless there is a significant performance advantage to using more RAM during non-finality, in which case the recommended specs should be changed
Steps to resolve
Unknown
The text was updated successfully, but these errors were encountered: