3 ms·
Erlang is pretty poor when it comes to P50 latency compared to C++ and Java. Part of this is due to BEAM being a pretty unsophisticated VM, and part of this is
by sargun 9y ago
Erlang is pretty poor when it comes to P50 latency compared to C++ and Java. Part of this is due to BEAM being a pretty unsophisticated VM, and part of this is due to the language and VM promoting inefficient patterns, (FP, immutability—these aren’t “bad”, just bad for our intel CPUs).
Hiring for Erlang can be difficult too.
That being said, Erlang is used heavily in FSI outside of HFT, or algorithmic trading. Several large FSI institutions are known users of Erlang (Visa, Banks).
- tankenmate 9y agoOne thing I have noticed that is mentioned less about immutable systems is the trade off of GC storm pause vs copy storm pause. Obviously system that use immutability either exclusively or primarily tend to use lazy evaluation to avoid copy storms sometimes it can't be helped. Mutability does have it upsides as well as down sides; the trade off isn't always obvious though.
- deleted 9y ago[deleted]