6 ms·
"It's certainly a common Erlang deployment pattern where no one Erlang process needs more than even a handful of megabytes necessarily, but the system as a whol
by jeffdavis 16y ago
"It's certainly a common Erlang deployment pattern where no one Erlang process needs more than even a handful of megabytes necessarily, but the system as a whole runs past several gigabytes by sheer scale of accumulated processes that themselves may only have hundreds of bytes allocated."
From the release notes, it looks like the 32-bit emulator restricts the total for all processes to 4GB. Only ETS tables and off-heap binaries don't count toward that total.
- jerf 16y agoThanks for the correction, re-reading it that seems likely. Less useful, then. Not useless (you can "cluster" Erlang with multiple instances on one system), but less useful.
- nivertech 16y agoIt's less usefull if you running a Web or Comet server (were you have one or more processes per client). It's usefull if you writing a control middleware handling a lot of data buffers, i.e. NoSQL database or MQ server.