well very nice post and the discussion seems to be very classic man keep up the good work and i wana say that post some more information about this topic actually i am a student and i love reading blogs because it provide great help and information man i am a student and recently completed my CISSP practice exams and i am really concerned about your post topic..!!!!!!

http://kenai.com/projects/jruby/pages/Benchmarks

The basic problems with your benchmark run are that the standard RBS suite runs each benchmark only once, and you did not run it with the –server flag to JRuby that turns on the optimizing JVM.

Each of the benchmarks is very short; this means that they will only rarely start to optimize. This obviously doesn’t reflect reality, since most applications people will run on JRuby will run longer than 5-10 seconds. In general to see the benefits of running on JRuby a benchmark needs to run long or be run repeatedly in the same JVM *without* redefining methods (which causes optimization to start over). RBS does neither of these.

The “–server” flag turns on the optimizing JIT in the JVM, where usually the less-optimized “client” JIT is used. “client” starts up faster, which is why we have it set as the default in JRuby.

Switching to –server and making the benchmarks run a few times each will at least double JRuby’s performance on most of these benchmarks.