News for hackers. Stuff that matters.
Re:Ruby Garbage Collection: Still Not Ready for Production by gdeglin on Friday March 28, 2014 @01:07PM (#7488504)
http://www.isrubyfastyet.com/ seems to show that Rails+JRuby performance remains disappointingly bad. The memory usage is kind of nuts too, not sure why it's so high.

Edit:

This page explains the high memory usage and it seems more reasonable now: https://github.com/jruby/jruby/wiki/Troubleshooting-Memory-U...

Re:Ruby Garbage Collection: Still Not Ready for Production by teacup50 on Saturday March 29, 2014 @12:36AM (#7491430)
These benchmarks are uselessly bad:

- The client connections are run without concurrency, serially, on the same machine: https://github.com/brianhempel/isrubyfastyet/blob/master/run...

- The JIT is only given 3 seconds to warm up: https://github.com/brianhempel/isrubyfastyet/blob/master/run... -- HotSpot kicks ass, but not after only 3 seconds of serially issued requests.

- By running the tests single-threaded, they're throwing away one of the major wins of the JVM -- low overhead concurrency.

Re:Ruby Garbage Collection: Still Not Ready for Production by RyanZAG on Friday March 28, 2014 @03:01PM (#7489264)
I think this would be a better benchmark than that one as it runs a more apples-apples comparison:

http://www.techempower.com/benchmarks/#section=data-r8&hw=i7...