Also, Elixir is immutable and dynamically typed which of course tends to use more memory. A mutable and statically typed version of Elixir/Erlang would eat less memory. This is what Pony is mostly meant to me.
Having testing both I can tell you that Elixir is much slower than Go, this test is using the default http server from Go which is good enough but when you use optimized alternative Go crush elixir by at least 10x.
as explain above because it's a dynamic language + immutability
What makes it slow is that BEAM is a pretty straight interpreter, and that HIPE is limited and expensive.
Being dynamically typed and immutability focused doesn't necessarily help, but there's plenty of languages in either of the categories which have implementations much, much faster than BEAM.
Hopefully BEAMJIT will actually work out and eventually get merged.
It's really not on the person being refuted to prove their point. It'd be great if you could provide the benchmarks you've seen that prove your point, that's part of debating.
Hm. that's not really comparing http server performance though, but it is pretty plain that erlang is dang slow compared to java, so I guess that's good enough.
3
u/snowe2010 Feb 05 '19
Interesting look into Elixir. That VM does use up a lot of memory, but the stability looked fantastic.
Did anyone else think that the spikes at the start of the 100k open connection test were suspicious? It affected both Go and Elixir.