Performing a comprehensive analysis of JVM garbage collection methods and systems reveals that several are classified as mostly concurrent — meaning garbage collection is intended to happen concurrently with application execution. However, 'mostly' concurrent isn't 'always' concurrent. Therefore, when GC modes get overloaded they revert back to 'stop-the-world' pausing to catch up. In these instances applications remain frozen while the garbage collection cycle finishes.
As the only fully concurrent JVM proven to work optimally for production server workloads, Azul's Zing uses an adaptive GC scheduling technique that leverages parallel processor resources to keep up. 'Quick release' allows for memory to quickly be freed for the application and relocation of objects, resulting in:
- Improvement of application performance
- Elimination of jitters, stalls, and pauses
- Optimization of capital investments
Find out what a comprehensive JVM garbage collection system analysis reveals by downloading this white paper.