Optimizer Hub runs as a shared service alongside your JVM fleet, not inside it. Two components split the work: Cloud Native Compiler and Ready Now Orchestrator. Cloud Native Compiler takes over JIT compilation, so JVMs can run in smaller, lower-cost instances. ReadyNow Orchestrator manages and distributes ReadyNow profiles across the fleet, simplifying deployment at scale. Together, they let every JVM start faster, warm up faster, and perform better.
Cloud Native Compiler shifts JIT compilation from individual JVMs to a centralized, scalable service, slashing CPU workloads and caching compilation for reuse. The resulting code runs faster, handles more traffic, and reaches full speed more quickly and smoothly. By eliminating CPU overhead, each JVM can be deployed in smaller instances and containers, reducing cloud costs. Compilation caching speeds up Java fleet warm-up times by 2x – 5x compared with standard OpenJDK installations.
ReadyNow, a feature of Azul Prime, reduces Java warm-up time by logging and reusing optimization profiles between JVM runs. ReadyNow Orchestrator delivers intelligent curation so each application uses the best profile to ensure consistent responsiveness, fewer errors, and higher SLA attainment during critical times like a retail rush, gaming traffic spikes, or market open.
Challenge: Inability to dynamically scale with confidence due to errors, timeouts during warm-up, and over-provisioned statically scaled fleet driving up cloud costs.
Solution: Optimizer Hub cut start-up and warm-up time dramatically, making scaling smoother and more predictable.
Benefit: Significantly lower compute requirements and 20%+ cloud cost savings.