Elixir is more focused on concurrent performance than raw performance. It’s still very fast but favors consistency above all else. I remember seeing a great benchmark that compared Elixir to Python and Go where they charted the variability of response times. Python and Go were very spikey with Go producing the fastest overall time. Elixir was extremely steady. Makes it an ideal choice for real time ops, holding millions of web sockets, ensuring a heavy process doesn’t affect the experience of everything else that’s executing.

You’ll also get natural clustering ability and a level of fault tolerance that’s almost silly.

I’ve been trying to find the time to demonstrate this with the tech empower benchmarks honestly. I want to see what will happen if you run all of them at the same time for a particular platform.

It baffles me how people give Elixir the credit for this. Everything you mentioned here have nothing to do with Elixir, but with how Erlang and its preemptive scheduler were optimized for soft real-time apps.

BEAM gets the credit but the parent mentioned Elixir so that’s how I responded. It’s just quicker than writing Elixir/Erlang/BEAM/OTP everytime.

Wasn’t trying to misappropriate the credit.

Agree that Erlang is what gives most of the performance and scalability benefits to Elixir and as such I should mention Erlang / BEAM to give due credit. However Elixir is my recommended target language for any developers who want an easy to learn language with a great community. The phoenix framework and powerful meta programming constructs are unique to Elixir.

Yep, Elixir mostly just changed the syntax to something more C like instead of ant turds. Erlang is a beautiful design but the prolog syntax never really caught on.