[erlang-questions] Garbage Collection, BEAM memory and Erlang memory

Roberto Ostinelli roberto@REDACTED
Wed Jan 28 14:42:57 CET 2015

On Wed, Jan 28, 2015 at 1:35 PM, Lukas Larsson <lukas@REDACTED>
> Could it be that you at this point trigger a lot of garbage collections
> due to calling erlang:garbage_collect/1? If you do that on a lot of
> processes at the same time you might get an explosion in eheap memory usage.

I constantly hibernate long term processes, all along the run. Nothing
specific happens after a while.

On Wed, Jan 28, 2015 at 1:35 PM, Lukas Larsson <lukas@REDACTED>
> If you cannot get a crash dump, I would look for changes in
> erlang:statistics/1 counters, to see if that can indicate if something in
> the system is changing drastically at that point, i.e. the number of
> reductions executed, the number of gc's done etc etc.

The number of reductions stay constant:

So does the number of GC:

The process count is always the same:

And the maximum message box length of any process in the system is always
between 1-3 (despite the peak at the start):

...Any other ideas? I'm getting appalled.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150128/48627198/attachment.htm>

More information about the erlang-questions mailing list