The most impact will be achieved on java standard library, like Streams (cited in the article). Right now, although their behavior is well stablished and they are mostly used in the "factory" mode (no user subclassing or implementation of the stream api), they cannot be shipped with the JVM already compiled.
If you can find a way (which this JEP is one way) to make the bulk of the java standard api AOT compiled, then java programs will be faster (much faster).
Also, the JVM is already an engine marvel (java JIT code is fast as hell), but this will make java programs much nimbler.
mshockwave · 1h ago
in addition to storing profiles, what about caching some native code? so that we can eliminate the JIT overhead for hot functions
EDIT: they describe this in their "Alternative" section as future work
nmstoker · 5h ago
Would be interesting if the Faster Python team considered this approach for Python (although maybe they already did?)
If you can find a way (which this JEP is one way) to make the bulk of the java standard api AOT compiled, then java programs will be faster (much faster).
Also, the JVM is already an engine marvel (java JIT code is fast as hell), but this will make java programs much nimbler.
EDIT: they describe this in their "Alternative" section as future work