News for hackers. Stuff that matters.
Re:JEP 295: Ahead-of-Time Compilation by WatchDog on Thursday October 27, 2016 @05:17PM (#12810263)
Hotspots aren't really going to be any faster with this change. The jvm already does a pretty good job of optimising hot code, which is why the vm is literally called hotspot.

AOT compilation is mostly intended to address startup time, Java has a big std library and much of it needs to be interpreted and compiled each time it runs. Between jigsaw modules and this, we should see some nice improvements in startup time.

Re:JEP 295: Ahead-of-Time Compilation by jjnoakes on Thursday October 27, 2016 @05:25PM (#12810354)
I don't think this is right, is it? I think this change is more about consistent performance than startup performance.

For me the JVM starts really quickly; the only performance issues I've seen there are related to large bloated frameworks doing too much at load time. I don't recall the std library being a factor at all (and why do you think it is recompiled every invocation?)

Re:JEP 295: Ahead-of-Time Compilation by WatchDog on Friday October 28, 2016 @03:49AM (#12813845)
The JEP explains it pretty clearly. "Improve the start-up time of both small and large Java applications, with at most a limited impact on peak performance."
Re:JEP 295: Ahead-of-Time Compilation by jjnoakes on Friday October 28, 2016 @08:56AM (#12815245)
Right. "Java Applications". Not the JVM.