5 ms·
The no VM thing I think is a downside. Sure raw performance is nice but not having a process eat all system cou resources is the true beauty of Erlang and Elixi
by jtwebman 4y ago
The no VM thing I think is a downside. Sure raw performance is nice but not having a process eat all system cou resources is the true beauty of Erlang and Elixir to allow you to self heal. Are you handling that with this library?
- deleted 4y ago[deleted]
- Fiahil 4y agoDocker and kubernetes are here for that
- paulgb 4y agoThey’ll give you ways to limit the CPU use of the OS process, but not the individual actor “processes” (Erlang overloads the term), which are opaque to k8s/linux/docker.
- snowboarder63 4y agoCan you give an example of what you're referring to? I don't know of anything limiting memory / cpu / etc in Erlang at least of any individual gen_server. We have the Factory processes which can gracefully loadshed, but that doesn't stop you from having a memory leak. At least Rust doesn't have a garbage collector, so when the actor is stopped + dropped, it'll cleanup not only it's state but also it's message queue's flushing them so that all memory is released at the time of drop.