3 ms·
> Funny, since for a long while, the "correct" way to run Ruby workloads in production was to run JRuby, therefore Java. cite please? I've worked with Rails s
by wlll 4y ago
> Funny, since for a long while, the "correct" way to run Ruby workloads in production was to run JRuby, therefore Java.
cite please?
I've worked with Rails since 2008 (as well as a lot of other languages) and JRuby has rarely been used.
- dijit 4y agojruby was definitely the play in 2008-2012, reason being that puma wasn't out yet and everything else was doggedly slow, so you used to use tomcat or glassfish. Since jruby is being interpreted into java (thus, bytecode), the resulting performance (throughput and latency) was a lot better and the lack of jemalloc (a good allocator by most means!) meant that your memory growth was a little more sawtooth and a little less... growy. I think these days most folks are just running something like puma.