3 ms·
>> "perf. is fine for most web apps for example." That same argument is made for Ruby and look at how many people leave due to slowness
by jerrycurly 8y ago
>> "perf. is fine for most web apps for example."
That same argument is made for Ruby and look at how many people leave due to slowness
- skrebbel 8y agoMany of them leave to a BEAM language actually, for speed reasons.
- jashmatthews 8y agoCRuby/MRI/YARV is almost as fast as BEAM at web stuff in terms of total throughput and JRuby is significantly faster. Sinatra + Sequel is faster at some things and slower at others. The default Rails setup makes huge tradeoffs away from performance.
- jxub 8y agoThe thing is that MRI Ruby is effectively single-threaded (unless you use things like concurrent-ruby which aren't that performant anyway) and threads can be blocked waiting for I/O, in fact they do most of the time, and is in I/O where Erlang really shines thanks to BEAM's nature of lightweight preemptive processes.
- jashmatthews 8y agoCRuby is multi-threaded with a GIL. CRuby also supports light-weight cooperative threads called Fibres, which are used to build things like: https://github.com/postrank-labs/goliath/ https://github.com/postrank-labs/goliath/ JRuby has no GIL, JIT, and is significantly faster than BEAM.