https://blog.devops-monk.com/tags/gc/Recent content in Gc on Devops MonkHugoen-usSun, 10 May 2026 00:00:00 +0000https://blog.devops-monk.com/tutorials/java25/generational-shenandoah/Sun, 10 May 2026 00:00:00 +0000https://blog.devops-monk.com/tutorials/java25/generational-shenandoah/GC Background: Why Generations Matter The Generational Hypothesis is the foundation of most modern GC design: Most objects die young. In a typical Java application, the vast majority of objects are short-lived: request/response objects, DTOs, builder instances, stream pipeline intermediates. They are created, used briefly, and then immediately eligible for collection. A GC that knows about this pattern can be far more efficient than one that treats all objects equally:https://blog.devops-monk.com/tutorials/java11/garbage-collection/Mon, 04 May 2026 00:00:00 +0000https://blog.devops-monk.com/tutorials/java11/garbage-collection/GC Changes Across Java 9–11 Release Change JEP Java 9 G1GC becomes the default GC JEP 248 Java 9 Unified GC logging (-Xlog:gc*) JEP 271 Java 10 Parallel Full GC for G1 JEP 307 Java 10 Application Class-Data Sharing (AppCDS) JEP 310 Java 11 Epsilon: No-Op GC JEP 318 Java 11 ZGC: Scalable Low-Latency GC (experimental) JEP 333 G1GC as Default (JEP 248, Java 9) G1 (Garbage-First) replaced Parallel GC as the default on systems with ≥2 CPUs and ≥2 GB heap.