3 ms·

JFYI, with podman [0] you can get all the security benefits mentioned in the article with containers. This is pretty neat and I love how cleanly the applicatio

by pm90 5y ago

JFYI, with podman [0] you can get all the security benefits mentioned in the article with containers. This is pretty neat and I love how cleanly the application code reads. I’m curious: is the Erlang VM super fast? I would have expected VM startup time to dominate the overall time to start. [0]: https://podman.io/ https://podman.io/

jacquesm 5y ago
The Erlang VM is plenty fast for starting stuff up that is long running, but I wouldn't use if for things that you need to launch 100's of times per second. But that's also not how it is intended to be used. As for the other kind of fast: number crunching performance is not what Erlang is for. It's for long running complex applications with a lot of moving parts, redundancy and extreme reliability.
- beedrillzzzzz 5y ago
  Numerical Elixir (NX)[1] is improving the number crunching situation! [1]: https://github.com/elixir-nx/nx/tree/main/nx#readme https://github.com/elixir-nx/nx/tree/main/nx#readme
brightball 5y ago
It's pretty quick on startup in my experience.
jolux 5y ago
Yes it does start fairly quick, nothing like the JVM. It's not nearly as fast while it's running, though. It only recently got a JIT, and currently doesn't do any optimization of the generated code.
hauleth 5y ago
I know about Podman, I just wanted to focus on systemd without additional tooling. Erlang VM startup is ok, but it is not ultra fast, and it can be easily slowed down with many modules in releases or slow applications. Additionally as it was said - Erlang works best in case of long-running instances where the VM is handling spawning and managing of short lived internal processes. First draft of this article also included the socket activation and FD passing section, but these were making the article way to long, so I moved them to the Part 2 where I will have more space for them. With socket activation Erlang VM startup time is negligible problem.

by pm90 5y ago

jacquesm 5y ago

The Erlang VM is plenty fast for starting stuff up that is long running, but I wouldn't use if for things that you need to launch 100's of times per second. But that's also not how it is intended to be used. As for the other kind of fast: number crunching performance is not what Erlang is for. It's for long running complex applications with a lot of moving parts, redundancy and extreme reliability.

beedrillzzzzz 5y ago
Numerical Elixir (NX)[1] is improving the number crunching situation! [1]: https://github.com/elixir-nx/nx/tree/main/nx#readme https://github.com/elixir-nx/nx/tree/main/nx#readme

brightball 5y ago

It's pretty quick on startup in my experience.

jolux 5y ago

Yes it does start fairly quick, nothing like the JVM. It's not nearly as fast while it's running, though. It only recently got a JIT, and currently doesn't do any optimization of the generated code.

hauleth 5y ago

I know about Podman, I just wanted to focus on systemd without additional tooling. Erlang VM startup is ok, but it is not ultra fast, and it can be easily slowed down with many modules in releases or slow applications. Additionally as it was said - Erlang works best in case of long-running instances where the VM is handling spawning and managing of short lived internal processes. First draft of this article also included the socket activation and FD passing section, but these were making the article way to long, so I moved them to the Part 2 where I will have more space for them. With socket activation Erlang VM startup time is negligible problem.