Java Ahead-of-Time Compilation with Oracle GraalVM

Java developers are familiar with the HotSpot VM's JIT (just in time) compiler which converts application bytecode into native machine code at runtime for optimal performance. Some of the drawbacks to this approach are large disk footprint, slow application startup, and significant memory overhead - all of which are problematic for microservices and other containerized workloads.
Did you know? Oracle GraalVM's high performance optimizing compiler can be used in both JIT and AOT (ahead of time) mode? GraalVM generated "native image" executables are compact, have instant startup, and consume a very small memory footprint since JIT compiler is not required.
Tune in to this 30-minute interactive session with Christian Wimmer, Consulting Researcher and Project Lead for GraalVM, to learn why GraalVM native image is leveraged by popular microservices frameworks like Micronaut, Helidon, Quarkus, and very soon Spring Boot. Join the discussion to review the JIT and AOT compilation techniques and explore their advantages, differences, and applicability.

[@nithinnambiar]

Why isn’t GraalVM suitable for large heap applications?

[@koutheir22]

Because the garbage collectors provided with the full OpenJDK runtime provide better performance and more configuration options.

[@nithinnambiar]

@@koutheir22 I gather the default option is serial GC which explains it. But G1 is supported in enterprise edition, so in theory it should work for large heaps no?