Thomas E Enebo wrote:
We turned on the JIT by default last night and we also did the brutal
threshold 0 (which forces every method the first time it is seen to be
JITd). We did this so we can ferret out any remaining issues with the
JIT. At this point we can run:
- All our tests (one small regression to figure out)
- Typical Rails applications
- Goldberg
- rake
- gem
Basically, things look really good. When we near release time we
will set the JIT threshold to a more sensible number.
If you have permgenspace problems, you may need to set the threshold
higher (JRUBY-900 explains why this is). We recommend for our sake
leaving it zero unless you are running something for a long period of
time which constantly redefines one-time user methods. We want as
much opportunity to find unsafe compilation as we can.
Or just apply the patch in JRUBY-900, which seems to resolve the permgen
issues that could happen in the most brutal cases...
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
