Why Your Java Applications Need Zing™

Many Java performance or scalability issues are not related to the application, database, network or container, but are more often related to the choice of the Java runtime or JVM. Conventional JVMs, such as HotSpot, have known limitations which can affect how a given application scales and performs under load. The most obvious and well-understood limitation is an application's memory heap size. Conventional JVMs are limited to only a few GB of heap memory before triggering execution pauses related to garbage collection (GC). While tuning may help, compaction is inevitable, which leads to inconsistent response time of the application that only gets worse under load or higher transaction rates.

Because of its unique design, Zing is the only JVM that can support virtually unlimited size heaps (over 300 GB) and eliminate stop-the-world GC pauses. The Zing JVM is optimized for Linux and x86 deployments and provides the most robust, elastic and scalable runtime for all enterprise applications. With Zing, your applications can achieve:

• Improved application execution and data caching through support for very large JVM heaps (over 300 GB)
• More consistent app response times even under load, via Azul's C4 pauseless Garbage Collector
• Reduced JVM tuning and faster time-to-deployment with an elastic and self-healing JVM whose performance is insensitive to conventional JVM parameters
• Ultra low latency, with Zing typically reaching 1-2 msec worst case pause times
• 50% reductions in TCO over existing runtime platforms through simpler deployments and better resource utilization
• Better application reliability and availability through a more robust and elastic JVM that can survive conventional or multi-tenancy "out-of-memory" errors
• Higher user density or transaction rates per instance through higher sustained allocation rates of the Zing JVM and C4 collector
• Dramatically faster production-time problem resolution via Zing's zero-overhead runtime diagnostic tools

Comparison of Zing and Conventional JVMs:

Next Step: What is Zing? »