On Thu, Feb 17, 2011 at 12:58 PM, Rémi Forax <[email protected]> wrote: >> fork is one way to address that, by keeping a "hot" VM and spawning >> instances of it, but JVMs that save their jit products (like Excelsior >> JET) do an excellent job too (once primed. JET starts up JRuby stuff >> *much* faster than Hotspot). ... > Charles, Is it not enough to have bytecode pre-compiled version > of your ruby files ?
In fact, verification of .class files is actually no faster than us simply parsing them from disk, and it's actually slower if we generate our own method handles for all method bodies contained therein. I've managed to get a fully-precompiled (i.e. .rb precompiled, handles pre-generated) script to start up as fast as parsed + interpreted, but only when the compiled Ruby .class is NOT verified. This also only addresses the issue of a cold parser and interpreter; cold core class logic still tends to dog JRuby for the first few seconds. - Charlie -- You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en.
