OOM events triggered due to Nomad RAM limits being ignored by Erigon

[C7-C5]

The RAM usage chart indicates repeated Out of Memory (OOM) events (represented by the red graph spikes) caused by Erigon's behavior. Erigon seems to only consider the total server RAM and disregards the specified limits.

Expected result:
Erigon should respect the RAM limits configured in Nomad and operate within the allocated memory boundaries, preventing OOM events.

Actual result:
Erigon ignores Nomad RAM limits and uses memory based on the server's available RAM, leading to OOM events.

[mandrigin]

okay, turns out it was because of rebuilding in memory

[revitteth]

I wonder if we can close - or is it worth investigating use of:

env {
  GOMEMLIMIT = "4GiB"
}