3 ms·
I've long thought that JVMs should do something similar within large organizations. There's a bit of a black art to exactly which optimizations in which order
by KMag 6y ago
I've long thought that JVMs should do something similar within large organizations. There's a bit of a black art to exactly which optimizations in which order are optimal, so it would help if there were some small amounts of randomization in that regard, along with performance monitoring/profiling and sharing across hosts / runs.
Of course, it's quite different when it's outside the organization if there's no way to opt out.
- pjmlp 6y agoThey already do, is what IBM calls cloud JIT on their JVM implementation. :) https://blog.openj9.org/2020/01/09/free-your-jvm-from-the-jit-with-jitserver-technology/ https://blog.openj9.org/2020/01/09/free-your-jvm-from-the-ji... Also the JIT cache that Hotspot now has, the original implementation was part of J/Rockit JVM.
- KMag 6y agoWait, I didn't realize they implemented a JIT cache before their AoT compilation option. It seems like pre-populating a JIT cache, dumping it to disk, and throwing that in as an extra resource in a JAR would have a lot fewer caveats than at least their first implementation of AoT Java compilation.