4 ms·
Erlang / Elixir processes use about 0.5kb per process, a preemptive scheduler on the BEAM to make sure work is consistent and isolated heap space for each one t
by brightball 3y ago
Erlang / Elixir processes use about 0.5kb per process, a preemptive scheduler on the BEAM to make sure work is consistent and isolated heap space for each one to avoid stop the world garbage collection.
It’s as good as it gets for this type of thing as it was designed for it from the ground up.
- tonyarkles 3y agoAnd it looks like the SystemLimitError issue they encountered is one flag away: https://elixirforum.com/t/too-many-processes-error/22224/2 https://elixirforum.com/t/too-many-processes-error/22224/2
- anonymousDan 3y agoThis was the first thing that occurred to me when I saw the error - should have been pretty straightforward to tweak the settings to give a clearer picture.
- pkolaczk 3y agoFixed already.
- tonyarkles 3y agoThanks! Looked back at the results and that's about what I'd expect. Erlang/Elixir isn't a silver bullet, but amazing in its own way for other reasons. Ultimate max performance and memory efficiency definitely isn't one of them :).
- masklinn 3y ago> Erlang / Elixir processes use about 0.5kb per process Last I checked it used about 2.5K. Beam reserves around 300 words per process (depends on exact options), but a word is 8 bytes not 8. You can get it lower (obviously at a cost as soon as you start using the process and need space) but nowhere near 512 bytes, just the process overhead is around 800.