Comments on: Nginx Passenger vs JRuby on Jetty http://letsgetdugg.com/2009/08/31/nginx-passenger-vs-jruby-on-jetty/ Random tech jargon Mon, 30 Jan 2012 20:30:22 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Chad Johnson http://letsgetdugg.com/2009/08/31/nginx-passenger-vs-jruby-on-jetty/comment-page-1/#comment-112 Chad Johnson Wed, 02 Sep 2009 03:02:33 +0000 http://letsgetdugg.com/?p=322#comment-112 There's a few tweaks to your JRuby opts that I would suggest. I would try using the latest 1.6 release first and foremost. 1.7 is still an unknown quantity at this time. Most people enjoying the performance benefits of JRuby are using it on 1.6 currently. I would also suggest benchmarking with and without -XX:+AggressiveOpts. That maybe hurting more than helping. JRuby is definitely higher than MRI on its memory requirements. If you can spare more than 384m to the JVM heap great. Give JRuby all you can. More specifically JRuby is very hard on the New (or Eden) generation of the heap. I set the new generation for my JRuby apps anywhere from 1/3 to 1/2 the total size of my heap. You can do that with : -Xmn192m. Here are a few other options than I am currently setting : -XX:ParallelGCThreads=8 (where 8 is the number of cpus/cores) -XX:MaxTenuringThreshold=15 (let objects sit in the new generation longer than they normally would, it will fill up soon enough causing a GC to kick in) There’s a few tweaks to your JRuby opts that I would suggest.

I would try using the latest 1.6 release first and foremost. 1.7 is still an unknown quantity at this time. Most people enjoying the performance benefits of JRuby are using it on 1.6 currently.

I would also suggest benchmarking with and without -XX:+AggressiveOpts. That maybe hurting more than helping.

JRuby is definitely higher than MRI on its memory requirements. If you can spare more than 384m to the JVM heap great. Give JRuby all you can.

More specifically JRuby is very hard on the New (or Eden) generation of the heap. I set the new generation for my JRuby apps anywhere from 1/3 to 1/2 the total size of my heap. You can do that with : -Xmn192m.

Here are a few other options than I am currently setting :

-XX:ParallelGCThreads=8 (where 8 is the number of cpus/cores)
-XX:MaxTenuringThreshold=15 (let objects sit in the new generation longer than they normally would, it will fill up soon enough causing a GC to kick in)

]]> By: victori http://letsgetdugg.com/2009/08/31/nginx-passenger-vs-jruby-on-jetty/comment-page-1/#comment-110 victori Tue, 01 Sep 2009 15:57:55 +0000 http://letsgetdugg.com/?p=322#comment-110 10,000 iterations? that is quite a lot. Servlet container restarts would be *really* painful if that is the case. 10,000 iterations? that is quite a lot. Servlet container restarts would be *really* painful if that is the case.

]]> By: Ben Noordhuis http://letsgetdugg.com/2009/08/31/nginx-passenger-vs-jruby-on-jetty/comment-page-1/#comment-109 Ben Noordhuis Tue, 01 Sep 2009 11:12:22 +0000 http://letsgetdugg.com/?p=322#comment-109 Victor, your benchmark is possibly flawed because (IIRC) JRuby with a default config only warms up after 10,000 rounds. What happens if you run ab with -n100000? Victor, your benchmark is possibly flawed because (IIRC) JRuby with a default config only warms up after 10,000 rounds. What happens if you run ab with -n100000?

]]>