-
Notifications
You must be signed in to change notification settings - Fork 981
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
Prysm Killed - Out of Memory #13964
Comments
@tunerooster What flags are you running with ? You can try with |
I will add: --enable-experimental-state but it may be a while before it happens again. Thanks for the suggestion. Do you know if this happens to others? |
There is a case here that happens when syncing: However it appears to be different to your case which appears to be more random |
I assume you noticed that prysm was using (or trying to use) almost 72GB. That would mean I would need 56GB of swap space (at least). I know nothing about prysm's memory requirements, but that seems like it could be a bug. My staking machine is maxed out at 16GB real RAM (it's a processor limitition I guess), but swap space should mitigate this, particularly for the few short times it neesd more than 16GB. However I hesitate to try to expand swap to, say 64G, without understanding if this is a good thing to do. I am running with the experimental flag now, so I'll report back with any results. |
That is the virtual memory @tunerooster , from the log prysm was trying to use 11gb of physical memory. The reason that virtual memory used by prysm is so big is because we use a memory mapped database(bolt). |
I see. So the mmap'd database is independent of swap but is still counted
as part of virtual memory. Thank you for clarifying that for me.
But then was prysm trying to use more than my 32GB of RAM + swap? 11GB
would not be a problem. What am I missing? Would adding even more swap
help?
…On Wed, May 8, 2024, 4:31 AM Nishant Das ***@***.***> wrote:
That is the virtual memory @tunerooster <https://github.com/tunerooster>
, from the log prysm was trying to use 11gb of physical memory. The reason
that virtual memory used by prysm is so big is because we use a memory
mapped database(bolt).
—
Reply to this email directly, view it on GitHub
<#13964 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADFMVIUEBRTG7UGJFON6LSLZBH5GTAVCNFSM6AAAAABHMAY4FWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBQGI3DONBXGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Every so often, from days to weeks, my beacon-chain process id killed, siting an OOM error. The kernel messages are:
Prysm Version:
beacon-chain version Prysm/v5.0.3/38f208d70dc95b12c08403f5c72009aaa10dfe2f. Built at: 2024-04-04 18:31:36+00:00
Geth Version:
geth version 1.13.14-stable
OS Release:
Linux u59 6.6.14-gentoo #1 SMP PREEMPT_DYNAMIC Sat Feb 3 03:06:01 MST 2024 x86_64 Intel(R) Celeron(R) N5095 @ 2.00GHz GenuineIntel GNU/Linux
The machine has 16GB RAM and 16GB swap. I recently increased swap from 6GB to 16GB, but it appears that is still not enough.
How much swap to you recommend to cover the worst case?
Thanks!
The text was updated successfully, but these errors were encountered: