On Thu, Jul 2, 2009 at 4:58 PM, Yoko Harada<[email protected]> wrote:
> OK, I understood what ruby2java does now. I expect ruby2java makes
> precompilation.
It may in the future, and there may be even a different approach to
generating Java classes from Ruby code. But at the moment it's a
fairly simple mechanism.
>> Are you interested in this to wire up the "compiled" logic in JSR223 or for
>> some other specific purpose?
>
> I want this for JSR223. If a compiled script runs faster than before,
> it would be a powerful feature for new JSR223 implementation.
>
> I'm wondering whether I should remove the feature to choose a mode
> among three from JSR223 implementation. People might expect that
> performance will improve, but the fact is not.
Well, it's not entirely true that performance won't improve. Compiled
(not necessarily precompiled) code does run faster than interpreted,
but since the JIT kicks in fairly quickly on almost all applications,
most people don't see the difference from precompiling. But
precompiled does have the benefit of avoiding the JIT warmup time,
plus it delivers bytecode to the JVM more quickly, meaning the JVM
itself can warm up faster. Eventual performance may or may not be
better, but it does eliminate some of the startup slowness.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
