Actually, someone came up to me after my presentation that had an internal application in production on JRuby on Rails. They had deployed on JRuby because they saw a performance increase in terms of reqs per sec vs MRI by doing so. It seems the performance story for JRuby right now is kind of in flux, with different apps getting very different results.
--Chris On Feb 1, 2008 7:25 AM, Alexey Verkhovsky <[EMAIL PROTECTED]> wrote: > On Jan 30, 2008 4:05 PM, Chris Nelson > <[EMAIL PROTECTED]> wrote: > > Here are the slides for a presentation I gave at the Columbus Ruby > Brigade > > this month. Some of them are recycled from previous talks by Charles > and > > Tom. BTW, for the performance demo I gave I used the quicksort > benchmark. > > JRuby 1.1RC1 totally smokes, I highly recommend it for demos: MRI: 5 > secs, > > JRuby: 0.99 secs on my dual core laptop. > > The problem with using microbenchmarks for performance demos is that > they are misleading. You can easily make some gullible person believe > that JRuby totally kicks MRI's ass performance-wise. Reality is not so > cool though: applications are typically a tad slower on JRuby than on > MRI. > > -- > Alexey Verkhovsky > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > RubyWorks [http://rubyworks.thoughtworks.com] > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > >
