If your Java-based operation is plagued by intermittent stalls, freezes, and jitter, and you’ve established that it is Garbage Collection (GC)-related, you have reached the right page. Whenever metrics matter, whether you have formal or informal service-level agreements for Java-based systems – Zing® is the ideal JVM for your operation. It removes GC as a factor impeding your business.
Zing also makes it possible to eliminate almost all of the JVM tuning that is necessary with legacy JVMs. Tuning JVMs can be tough, and making sure you are making the right choices among dozens of flags and settings is problematic. There’s a lot of Java tuning lore out there – some of it valid, some years out of date, however if you’ve gotten this far it is because you need to make things happen for your Java-based business. There’s a better alternative: Zing.
1. With Zing, you can take GC tuning off the table. Permanently.
Zing doesn’t use obsolete GC technology – the Azul C4 collector can NEVER “stop the world”
No need to re-architect your application – use the working code you have
No need for additional third-party products or off-heap kludges – Zing just works
Zing is Java SE compliant – it meets the standards and passes the tests for Java SE 6 or 7
And your peak latencies and outliers get much closer to your average latency
2. With Zing, you can deliver consistently better latency.
Deliver the same level of performance at the 99.9th percentile as at the 90th
Meet the needs of trading systems, matching engines, and other peak-latency-sensitive apps