M C wrote:
*/Charles Oliver Nutter <[EMAIL PROTECTED]>/* skrev:
So many options, so little documentation!
Yes, if you AOT compile, you avoid the JIT cost of one Java class being
generated per method. However the methods generated into that class
still need to be bound into DynamicMethod objects somehow, so we
generate a class-per-method for the handles. In general, this should be
cheaper.
You can also AOT compile and turn on reflection, which will mean no
generation of handles at runtime other than additional methods that
might JIT.
Interesting topic! What is your recommendation regarding possible AOT
compile for a rails project deployet as a war on a java app server using
JRuby? I.e. Would that be beneficial for performance/gc etc ?
Well at the moment I'm not sure a full AOT of a rails app is possible
Rails uses a lot of filesystem tricks to load its libraries, which means
that turning them into classes would probably interfere with loading.
In general AOT is going to be great for large single applications, where
you can have the whole app load up and execute. I'm also looking for
folks to play with it, try it out, and see what more needs to be done to
improve it. It's also certainly possible we could have it generate all
method handles up front to avoid generating them at runtime.
There's lots of room for ideas :)
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
