Peter Williams wrote:
Just an FYI, it is possible to profile "deployment of a rails app to
V3", using the NetBeans Profiler and the V3 plugin. 99% of what this
measures is Rails startup, as invoked by JRuby.
I actually did this a while back to see whether the results had any
value for end users (doubtful - it just shows JRuby interpreter over and
over). I'll poke around to see if I still have the saved stats. It
might have value for your team. It should be easy enough to recreate.
It's just a bit time & memory consuming while the profiler instruments
things and you have to manually attach the profiler to V3 since Rails
project has no profiler integration points.
Yeah, if you want to publish profile snapshots that would be great. It
kinda fits into what we know of JRuby and JVM though:
* JVM takes a while to warm up, so even JRuby code that's fast later is
slow at the beginning
* JRuby interprets at first, so doesn't run at full speed immediately
* Even though interpreter is faster than MRI, that's faster when warmed
up; it's still slower initially
* Every incremental improvement we make to interpreter performance (of
which there have been many in 1.1.3 and 1.1.4) will help startup time
I think there's still a lot of runway left for startup performance, but
there's a glass ceiling imposed by the JVM on how much improvement we
can make. Profiles like yours might help us see specific areas in the
interpreter that are coming up as bottlenecks.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
