You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted you to know that our app is now running fairly cleanly in local development on my laptop!
Congratulations: this is the first time I've seen Rubinius 2.2.6 outperform 2.1.1, with Rubinius clocking in at 676 req/second and 2.1.1 at 428 req/second.
Rubinius serves nearly 58% more req/sec!
Rubinius used around 2.3x as much CPU capacity as MRI did, so 2.1.1 remains more processor efficient, but it sure is nice to to see Rubinius doing more work by using more cores, and knowing that it can only get better from here.
I distinctly remember Rubinius being hundreds of times slowing that MRI back in the day! :-)
The only issues that currently stand in the way of deploying on Rubinius are:
Rubinius memory use appeared to be ever expanding, exceeding 700MB at the end of the run, whereas 2.1.1 quickly grew to 45MB and was rock steady at that number for the rest of the run
Finally, while it wouldn't prevent me from deploying, it's interesting to note the longest transaction times number, where 2.1.1 has a 50ms(ish) maximum request duration, compared to Rubinius' 150ms(isn) max
Hey all.
I wanted you to know that our app is now running fairly cleanly in local development on my laptop!
Congratulations: this is the first time I've seen Rubinius 2.2.6 outperform 2.1.1, with Rubinius clocking in at 676 req/second and 2.1.1 at 428 req/second.
Rubinius serves nearly 58% more req/sec!
Rubinius used around 2.3x as much CPU capacity as MRI did, so 2.1.1 remains more processor efficient, but it sure is nice to to see Rubinius doing more work by using more cores, and knowing that it can only get better from here.
I distinctly remember Rubinius being hundreds of times slowing that MRI back in the day! :-)
The only issues that currently stand in the way of deploying on Rubinius are:
Finally, while it wouldn't prevent me from deploying, it's interesting to note the longest transaction times number, where 2.1.1 has a 50ms(ish) maximum request duration, compared to Rubinius' 150ms(isn) max
Ruby 2.1.1
Rubinius 2.2.6
The text was updated successfully, but these errors were encountered: