Prysm Killed - Out of Memory about prysm

[tunerooster]

@tunerooster What flags are you running with ? You can try with --enable-experimental-state to see if it helps reducing resource consumption by prysm

beacon-chain --p2p-max-peers=150 --pprof --execution-endpoint=http://localhost:8551 --jwt-secret=/mnt/crypto/.ethereum/keystore/jwt.hex --datadir /mnt/crypto/.ethereum/prysm --suggested-fee-recipient 0x68...faeB

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?

[nisdas]

@tunerooster What flags are you running with ? You can try with --enable-experimental-state to see if it helps reducing resource consumption by prysm

[nisdas]

There is a case here that happens when syncing:
#13963

However it appears to be different to your case which appears to be more random

[tunerooster]

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.

[nisdas]

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).

[tunerooster]

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: ***@***.***>