JVM Startup Optimization and Virtual Threads (Java 21)

Modern JVM performance optimization addresses two distinct goals: faster startup time (targeted by AOT compilation, AppCDS, and Spring AOT) and higher concurrency without scaling thread counts (addressed by virtual threads in Java 21+). These are separate problems solved by separate mechanisms.

Startup optimization options:

• AppCDS: capture loaded classes once, build a shared archive, subsequent launches memory-map instead of re-parsing; cuts startup 20-40%
• Spring Boot AOT: generates bean definitions at build time, eliminating runtime reflection scanning
• GraalVM native image: sub-200ms startup; demands explicit reflection configuration for all dynamic access

Virtual threads (Java 21):

• JVM-managed lightweight threads mounting onto a small pool of carrier threads (~N cores)
• Blocking I/O parks the virtual thread and frees the carrier — existing synchronous code scales to thousands of concurrent I/O operations
• No reactive rewriting needed — keep your blocking JDBC calls and HTTP clients

Thread pinning (main migration concern):

• synchronized block pins the virtual thread to its carrier — cannot unmount; if the block contains I/O, the carrier is wasted
• Fix: replace synchronized with ReentrantLock on I/O-heavy paths
• Enable -Djdk.tracePinnedThreads=short during testing to detect pinning before production

I recommend AOT for startup-sensitive deployments and virtual threads for I/O-heavy services. Audit all ThreadLocal usage — each virtual thread maintains its own copy, which can waste memory at scale.