On 9/4/07, Alexey Verkhovsky <[EMAIL PROTECTED]> wrote: > > Can you try hitting like 100,000 to get an > > idea if hotspot starts warming more. > Sure. > > Actually, most time-consuming methods (from profiler point of view) > get 5- or 6-digit number of hits during a thousand page hits, anyway. > I'll test it though.
So, I did. After the first thousand hits, all performance metrics improve by about 4% in the next 700 hits, after which they didn't change at all. Conclusions: 1. The right number number of page hits to warm up the JIT compiler in Rails benchmarks is 2000. 2. This information doesn't really change the big picture portrayed earlier in this thread. As a sidenote, I've done a similar quick-n-dirty Petstore shootout with MRI+Rails vs lean and mean Java (Clinton Begin's JPetstore 5.0). The latter is ~3 times faster. I don't have a burning desire right now to install a full blown J2EE server and deploy Sun Blueprints classic on it :), but from what I remember, this makes MRI+Rails approximately as fast as J2EE. So (as I always said) if J2EE was fast/scalable enough for The Enterprise 8 years ago (despite the much slower hardware), surely Rails is fast/scalable enough for it now. -- 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
