Memory allocator limits for low‑traffic Erlang workloads
The primary goal is to keep the memory footprint of a low‑traffic Erlang node minimal so that hosting costs can be reduced. Erlang’s lightweight processes normally require roughly 1.5 KB of heap, but the default runtime allocator (erts_alloc) can over‑allocate for short‑lived processes, inflating the resident set size on nodes that handle only a handful of c