JVMs can easily make use of a 100 GB heap but pause times for GC can be many minutes in length. This limits application performance and scalability and prevents Java applications from using the full resources of today’s commodity servers. Very large heap sizes are often very practical, if you can eliminate the associated performance issues. Azul Zing® is the first JVM to solve the problem of GC pauses and allow heaps up to 8 TB without performance penalty.
A larger Java memory heap
A smaller Java memory heap
“We’re achieving unobtainable technical feats with Azul Zing that you can’t achieve using plain vanilla Java. And this performance translates into huge infrastructure savings and simplification by having less servers. With Azul, we were able to reduce our front-end server footprint by more than 30%, which is hundreds of servers, and our database server footprint by about 50%.”
We’ve found plenty of evidence to indicate the pent-up demand for more heap:
The problem is in the software stack, which places artificial constraints on memory per instance. GC pause time is the only limiting factor for instance size, and as we’ve found in practice, even extensive garbage collection (GC) tuning doesn’t make it go away. Once you’ve solved GC, you’ve solved the problem. Azul’s innovative C4 garbage collection algorithm is fully concurrent, eliminating the performance impact of very large heaps.
The paper concludes with some pitfalls, common misconceptions, and “myths” around garbage collection behavior, as well as examples of how certain choices can result in impressive application behavior…Get Your Copy