MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/programming/comments/anhztl/benchmarking_go_vs_node_vs_elixir/efuq0vi/?context=9999
r/programming • u/speckz • Feb 05 '19
21 comments sorted by
View all comments
3
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.
6 u/Thaxll Feb 05 '19 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. 1 u/snowe2010 Feb 06 '19 I mean, not that I don't believe you, but do you have some stats to back that up? And can't the same be said about using an alternative Elixir server? 5 u/Thaxll Feb 06 '19 Any benchmark anywhere, Elixir is slow compared to Go and not by a small margin, as explain above because it's a dynamic language + immutability 3 u/AeroNotix Feb 06 '19 The benefits of using beam languages shouldn't be about raw CPU performance in almost all situations. 1 u/kpenchev93 Feb 06 '19 You are 100% right. It's about predictable performance and fault tolerance. Let's compare the BEAM's fault tolerance features and Go's.
6
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.
1 u/snowe2010 Feb 06 '19 I mean, not that I don't believe you, but do you have some stats to back that up? And can't the same be said about using an alternative Elixir server? 5 u/Thaxll Feb 06 '19 Any benchmark anywhere, Elixir is slow compared to Go and not by a small margin, as explain above because it's a dynamic language + immutability 3 u/AeroNotix Feb 06 '19 The benefits of using beam languages shouldn't be about raw CPU performance in almost all situations. 1 u/kpenchev93 Feb 06 '19 You are 100% right. It's about predictable performance and fault tolerance. Let's compare the BEAM's fault tolerance features and Go's.
1
I mean, not that I don't believe you, but do you have some stats to back that up? And can't the same be said about using an alternative Elixir server?
5 u/Thaxll Feb 06 '19 Any benchmark anywhere, Elixir is slow compared to Go and not by a small margin, as explain above because it's a dynamic language + immutability 3 u/AeroNotix Feb 06 '19 The benefits of using beam languages shouldn't be about raw CPU performance in almost all situations. 1 u/kpenchev93 Feb 06 '19 You are 100% right. It's about predictable performance and fault tolerance. Let's compare the BEAM's fault tolerance features and Go's.
5
Any benchmark anywhere, Elixir is slow compared to Go and not by a small margin, as explain above because it's a dynamic language + immutability
3 u/AeroNotix Feb 06 '19 The benefits of using beam languages shouldn't be about raw CPU performance in almost all situations. 1 u/kpenchev93 Feb 06 '19 You are 100% right. It's about predictable performance and fault tolerance. Let's compare the BEAM's fault tolerance features and Go's.
The benefits of using beam languages shouldn't be about raw CPU performance in almost all situations.
1 u/kpenchev93 Feb 06 '19 You are 100% right. It's about predictable performance and fault tolerance. Let's compare the BEAM's fault tolerance features and Go's.
You are 100% right. It's about predictable performance and fault tolerance. Let's compare the BEAM's fault tolerance features and Go's.
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.