@nyanide @prettygood I've seen beam get hungry for memory for no reason, oom and be fine for weeks again multiple times. It went from maybe a gigabyte of allocated memory to 4x of that in a minute.

I don't think it likes running with other applications on the same host like with the process spin trick it uses to convince the kernel scheduler to not pause the process and give the resources to something else. There might be some obscure argument for it, but who the fuck knows those.