Garbage Collection Programming

Solving Garbage Collection Programming Issues

Almost all garbage collection programming involve attempts to hold off on compaction. This can be accomplished for a while, but there will come a time when application processing has to halt to identify which objects are still being deployed. y need to then be collected, and the heap de-fragmented and compacted.  The bigger the heap, the longer the pause times, which will result in noticeable delays for users and poor application performance.

Azul’s Zing® default garbage collection program, C4 (Continuously Concurrent Compacting Collector), increases performance and removes barriers to scalability of Java by removing pause times even at large memory heap sizes. This technology combines software techniques and hardware emulation features to support ‘concurrent compaction’, allowing applications to keep on processing while remapping memory.

Some of the benefits of Zing’s pauseless garbage collection include:

  • consistent garbage collection (GC) behavior
  • predictable application performance and response times
  • smooth scaling from 1GB to over 1 TB memory heap sizes
  • reduced garbage collection (GC) tuning and JVM tuning

To learn more about Java garbage collection and the variations between collection programming algorithms, watch this video from Gil Tene, Azul's CTO: Understanding Java Garbage Collection.

© Azul Systems, Inc. 2017 All rights reserved.