Out of memory (OOM) - Prysm killed about prysm HOT 5 CLOSED

@GavinStein1 16gb should be more than enough, do you know what is the current resource consumption by each process ?

from prysm.

Thanks @nisdas for the response. From monitoring usage (by calling top command) Prysm starts around 28% and as syncing progresses it is reaching 50%+. I've only monitored usage while syncing because I've never reached the finish before it gets killed. For Geth, when synced it sits around 30% too. I think it might be a combination of concurrent spikes in memory usage by Prysm and Geth (and likely the same when I was operating Lighthouse).

I think you're right in saying that 16gb should be more than enough but I think 32gb would likely resolve this issue. For now, I'll keep monitoring and share any clues I find here.

from prysm.

Thanks for the clarification @GavinStein1 , can you try running with --enable-experimental-state ? It should help with memory consumption here

from prysm.

Tried that flag but still the same issue. I am gonna try Nimbus as the client and see if i still have the same issues, might be able to help determine if it is my machine that is the issue. Gonna take a while to sync so I will have an update when that is done.

from prysm.

I've been able to successfully sync and stay connected running geth with nimbus. There are spikes in memory usage usually from geth. My best guess is that simultaneous spikes in geth and prysm caused the crashing, but I do not have the expertise to investigate further. I am going to close this issue, apologies I don't have any better answers for anyone else having this problem.

from prysm.