5 ms·
> No dynamic byte code (Lambda Expressions, Dynamic Classes, etc.) That just means it won't be AOT compiled. The JVM can still JIT them. > No decrease to JVM
by the8472 10y ago
> No dynamic byte code (Lambda Expressions, Dynamic Classes, etc.)
That just means it won't be AOT compiled. The JVM can still JIT them.
> No decrease to JVM start up times
The JVM itself starts quite fast. Most of the time spent in startup comes from the applications themselves. Spend a lot of time in the interpreter running their startup code and burning CPU cycles on the lower compiler tiers.
> The only supported module is java.base
Supported in the sense of oracle offering support. You can still compile other modules. It's just experimental.
- bluejekyll 10y ago> The JVM itself starts quite fast. Most of the time spent in startup comes from the applications themselves. Jar unpacking can contribute quite a bit to startup times. It would be neat if this also did a pre-linked library as well.
- lern_too_spel 10y agoAn optional link step at build time is coming in Java 9. http://openjdk.java.net/jeps/282 http://openjdk.java.net/jeps/282
- paulddraper 10y agoSo if you use .class files instead of .jar files, you'll start up significantly quicker?
- bluejekyll 10y agoYes. In fact many systems unpack jars to a temporary directory first for this reason. edit: I should add that this really only matters for large numbers and sizes of jars.