I cannot understand why JVM sticks to JIT. JIT's advantage is mainly portability of intermediate code. So once intermediate codes are deployed in server, I don't care whether pre-compile takes 30 minutes or not if memory allocation and computation become more efficient. However this might be stupid idea.
Re:Why I Don't Use The JVM
by benjiweber on Monday November 14, 2011 @05:58PM
(#3236091)
JIT allows a range of optimisations that are not possible with AOT compilation. A JIT has access to more information at runtime such as profiling data and so can perform more informed optimisations. It can also change over the lifetime of the programme if observations change.
Some interesting stuff here http://wikis.sun.com/display/HotSpotInternals/PerformanceTec...
Java can't do this because Java self-modifies code (JIT) to run faster while it's running. Once all your classes are loaded into ram though, the memory gets consumed at a much more leisurely pace. However, multiple apps can't reuse each other's already mapped into memory code like they can with PHP, etc. As far as appserver restarts, just pay the money for JRebel already and quit complaining. Your life will be so much better.