> Elixir has it all (well, almost). It's fast, it's [...]
Dude, Elixir compiles to BEAM, it's slow as hell. Have you ever compared its
processing speed with virtually anything else? It's not processing speed that
Erlang is sold about.
A bit of an exaggeration. It's not as fast at math as Java. It's quite faster than Ruby (while keeping coder-friendly features such as auto-rollup to bignums). If you use pattern-matching correctly, it is EXTREMELY fast at I/O or binary parsing. That puts it in a unique space of "people who don't want to sit on the JVM yet want a fully-functional language that has an accessible syntax AND macros AND massive concurrency"... Web developers, basically.
My experience with Clojure ended when I got a blown-up gross Java stack trace because I went out of bounds on the underlying Java int representation. Fuck that, I consider that "janitorial duties" and not something I should be responsible for as a programmer. YMMV. No offense to you C guys. ;)
Actually, no. Last time I compared BEAM (Erlang) and something else, Erlang
code that only parsed text data from a file (CSV) was several times slower
than Perl script that parsed that, built a structure, serialized it, and wrote
back to a disk file (BerkeleyDB).
> It's quite faster than Ruby (while keeping coder-friendly features such as auto-rollup to bignums).
I doubt it, unless Ruby (MRI is what I think of) is an extremely poorly
written interpreter.
> If you use pattern-matching correctly, it is EXTREMELY fast at I/O or binary parsing.
It's not. It's slow (I've seen it when comparing with other runtimes). It was
never intended to be fast. It was always intended to be convenient and
highly concurrent.
> Actually, no. Last time I compared BEAM (Erlang) and something else, Erlang code that only parsed text data from a file (CSV) was several times slower than Perl script that parsed that, built a structure, serialized it, and wrote back to a disk file (BerkeleyDB).
Yeah, Erlang/Elixir are both not very fast when it comes to stuff like file parsing. Jose, the creator of Elixir pointed that out several times before. But as mentioned before, web developers can greatly benefit from Elixir.
> I doubt it, unless Ruby (MRI is what I think of) is an extremely poorly written interpreter.
I wrote several things in both languages. CSV parsing is pretty much the same speed, again file handling in Erlang/Elixir. When it comes to real web apps, Elixir is usually faster by a factor of 10x when DBs are involved and 100x when it comes to plain rendering.
> It's not. It's slow (I've seen it when comparing with other runtimes). It was never intended to be fast. It was always intended to be convenient and highly concurrent.
As others have mentioned, depends on what you think is fast and in what areas. When it comes to web apps, Elixir is way faster than ruby, python and even node. Pattern matching, for instance used for router matching is very fast compared to the techniques used in ruby/python frameworks.
Java, Go and several other languages are faster as Erlang/Elixir, of course. But Go is too low level for huge apps and Java is a whole different beast. Basically, Elixir is a nice middle ground to develop fast-enough web apps with high concurrency and easy scalability without sacrificing dev speed and dev fun.
> But as mentioned before, web developers can greatly benefit from Elixir.
I'm not saying they wouldn't. I just object against calling Elixir "fast",
because it's not. It's just used in the places where raw sequential processing
speed is not what makes the difference. It only makes up for that loss because
it doesn't degrade when the same procedure is executed many times
simultaneously, which is very hard for anything that's not BEAM (or Go, so
I hear).
>> I doubt it, unless Ruby (MRI is what I think of) is an extremely poorly written interpreter.
> I wrote several things in both languages. CSV parsing is pretty much the same speed, again file handling in Erlang/Elixir.
Funny. I expected MRI to be as fast as Perl or Python. What you say means it's
much slower.
> When it comes to real web apps, Elixir is usually faster by a factor of 10x when DBs are involved and 100x when it comes to plain rendering.
Unless I see how the comparison was arranged, I have trouble to believe that.
I've seen BEAM being very slow for sequential workload, and there's no
mechanism that would explain the speedup right off the bat, barring the
possibility of comparison looking at apples and oranges (e.g. comparing raw
SQL queries in Elixir to Django's ORM).
1) The situation might have changed since you looked at this
2) The algorithm to do the work might have been suboptimal (for example, not taking advantage of pattern-matching, or using regex which everyone agrees is too slow in Erlang/Elixir)
1) It might, but I doubt BEAM got rewritten in that extent.
2) Split on a comma is very hard to get suboptimal, especially when it was
`string' module supplied by Erlang.
3) Half of those fiddly techniques will be very, very hard to use in Erlang
(I understand that the thread is about Elixir, so you sort of assumed that
I was talking about it even though I explicitly said that it was Erlang and
BEAM code). Then, the load was on the CPU, not I/O. Reading the file upfront
was not going to help.
I don't know why you're getting downvoted just for dissenting. I don't want HN to be another damn Reddit echo chamber. Lots of criticisms of popular things are valid. I thought we were just having a civil discussion, but now I'm angry BECAUSE you got downvoted lol
But I would still like to see any evidence from you if you'd like
Tl;dr: Elixir is a bit faster than Ruby for straight up File IO if you really know what you're doing. Naive approaches in Elixir can lead to terrible performance.
I'm a huge fan of Elixir, but eeking out better performance can require some tricks that aren't intuitive if you're new to the language.
From personal experience (we're using Elixir at work) and we compared parsing a CSV in Elixir vs Scala, and the Elixir version was about 20% slower. However, for our use cases, we can more than make up for it by parellelizing processing downstream, ie: the csv parsing wasn't going to be the bottleneck anyway - other things, (which are easily parallelizable if you're running on BEAM) are the bottleneck, so BEAM gives us some nice things the JVM doesn't.
From what I read, Elixir is very fast at I/O based tasks, especially when there is lots of blocking involved. For example orchestration layers that push data between various API's and/or handle many concurrent connections.
Languages that compile to the JVM like Scala or Clojure (or Java of course) will probably be faster for computation.
I see Elixir as being suitable for the same category of applications as nodejs.
> From what I read, Elixir is very fast at I/O based tasks, especially when there is lots of blocking involved.
Now make two steps back and read this again. What you say is that Elixir is
"very fast" when it comes to tasks when Elixir pretty much doesn't do
anything, so it being fast or slow doesn't matter. Hardly a definition of
"fast".
But it is actually true for BEAM machine. It was never intended to be fast, it
was intended for running many tasks at the same time (so that none of them
starves others for any reason).
Slow as hell is a very scientific measurement :) Processing speed for what workload on what hardware? You do realise there are a lot of workloads that need to be optimised for latency? If we take web dev. Phoenix based solutions are about on par with one's based on a typical Go framework like Gin and are significantly faster than something using PHP, Ruby, Node, Python based web frameworks for a real world workload.
> Slow as hell is a very scientific measurement :)
On par with the claim that "Elixir is fast".
> Processing speed for what workload on what hardware?
Sequential processing, what did you think? BEAM excels at running many
sequential processes at the same time, it would be very hard to match that.
(And that's why for text processing I use Perl or sometimes Python, but for
services that pass data back and forth through network I use Erlang.)
Dude, Elixir compiles to BEAM, it's slow as hell. Have you ever compared its processing speed with virtually anything else? It's not processing speed that Erlang is sold about.