2 ms·
Note that you aren't tied to Java 8, which is quite old by now, but can also run GraalJS with OpenJDK 11, 12, 13, and enjoy the recent performance improvements
by pron 7y ago
Note that you aren't tied to Java 8, which is quite old by now, but can also run GraalJS with OpenJDK 11, 12, 13, and enjoy the recent performance improvements to the GC (using ZGC or Shenandoah) and startup time (using Application CDS):
https://github.com/graalvm/graal-js-jdk11-maven-demo https://github.com/graalvm/graal-js-jdk11-maven-demo
- kvlr 7y agoAh nice, we do want to switch Nextjournal to Shenandoah eventually after reading http://clojure-goes-fast.com/blog/shenandoah-in-production/ http://clojure-goes-fast.com/blog/shenandoah-in-production/ So is graal polyglot already compatible with newer JDKs and it's just native image generation that's blocking the upgrade? https://github.com/oracle/graal/issues/651 https://github.com/oracle/graal/issues/651
- pron 7y agoNative image is experimental, and I believe is a separate download now. Maybe someone from the Graal team can give more precise information about what exactly works in stock OpenJDK, but you should try that demo with Java 12 (or even 13). While you're at it, also give ZGC a try (see https://news.ycombinator.com/item?id=19886856 https://news.ycombinator.com/item?id=19886856 and http://www.programmersought.com/article/8311115057/ http://www.programmersought.com/article/8311115057/).
- grashalm 7y agoGraal-dev here, We are working with a very high priority on JDK 11 support. We should be able to ship it in a few months from now. > So is graal polyglot already compatible with newer JDKs and it's just native image generation that's blocking the upgrade? Not just. We also need to upgrade the JVMCI version we use in order to support libgraal (Graal compiler as native-image in HotSpot). Also, modules make everything a little bit more complicated as well.