There is no reason that a hotspot-ish JVM can't store it's dynamically-optimized class files in some kind of repository and use those files instead of the original ones. The optimized class files could then "evolve" into efficient [byte]code. The JVM would maintain some state with each optimized class file indicating how "optimal" it is. Starting with 0%, the JVM then optimizes less-and-less aggresively until it reaches some threshold value (e.g. 95%), and then the optimizer just stops trying (so it doesn't steal cycles). If the JVM indexed the repositories on a per-main-method basis, it would even allow for shared libraries that are optimized seperately for specific programs. If your disk-space is cheap and your time is expensive, I would think that this is the way to go. Vendors of software implemented in Java could even give their users "static optimization profiles" based on their in-house testing to give these advanced JVM's a head start.
Slashdot Mirror
There is no reason that a hotspot-ish JVM can't store it's dynamically-optimized class files in some kind of repository and use those files instead of the original ones. The optimized class files could then "evolve" into efficient [byte]code. The JVM would maintain some state with each optimized class file indicating how "optimal" it is. Starting with 0%, the JVM then optimizes less-and-less aggresively until it reaches some threshold value (e.g. 95%), and then the optimizer just stops trying (so it doesn't steal cycles). If the JVM indexed the repositories on a per-main-method basis, it would even allow for shared libraries that are optimized seperately for specific programs. If your disk-space is cheap and your time is expensive, I would think that this is the way to go. Vendors of software implemented in Java could even give their users "static optimization profiles" based on their in-house testing to give these advanced JVM's a head start.
If it is a parody, isn't it protected by free speech laws?