JVM & Memory

102. GraalVM Native Image vs HotSpot JIT

GraalVM Native Image compiles Java bytecode ahead-of-time (AOT) into standalone native machine binaries, achieving instant startup (<10ms) and minimal memory footprints at the expense of dynamic runtime optimizations.

Java 21+ (GraalVM CE & Oracle GraalVM)

Explanation

Traditional Java runs on the HotSpot JVM, loading .class files dynamically, interpreting them, and relying on JIT compilation (C1/C2) to optimize hot loops. While this produces world-class peak throughput through runtime profiling, it incurs a startup latency penalty ("warm-up time") and substantial baseline memory footprint (JVM metadata, JIT compiler threads, class tables).

GraalVM Native Image uses Ahead-Of-Time (AOT) compilation to convert Java applications directly into native platform executables (ELF on Linux, Mach-O on macOS, PE on Windows). AOT compilation performs closed-world analysis: it traces all reachable classes, methods, and fields from main() and strips everything else, eliminating the JVM runtime entirely.

Tradeoffs in interviews: - Native Image Advantages: Instant sub-10ms startup, tiny memory footprint (ideal for AWS Lambda, Kubernetes pods, serverless scale-to-zero), compact container images, no JIT CPU spikes at boot. - HotSpot JIT Advantages: Higher peak throughput on long-running services (JIT leverages actual runtime branch frequency and hardware profile), full dynamic reflection/classloading without static metadata configuration, mature profiling tools (JFR, remote JMX). - Native Image Constraints: Reflection, dynamic proxies, and JNI require explicit reachability metadata JSON files (reflect-config.json).

Example

// Native Image friendly code avoids unbounded dynamic reflection:
public class NativeImageApp {
    record Greeting(String message, long timestamp) {}

    public static void main(String[] args) {
        long start = System.currentTimeMillis();
        Greeting g = new Greeting("Hello from GraalVM Native Image!", System.currentTimeMillis());
        long elapsed = System.currentTimeMillis() - start;

        System.out.println(g.message() + " (initialized in " + elapsed + " ms)");
        System.out.printf("Total memory allocated: %.2f MB%n",
            (Runtime.getRuntime().totalMemory() - Runtime.getRuntime().freeMemory()) 
            / (1024.0 * 1024.0));
    }
}
// Build with: native-image -O3 -march=native -jar app.jar
// Result: A standalone executable with zero JVM dependency!

Sources