Garbage Collectors: Battle Royale
summary
Overview of automatic memory reclamation history leading into Java garbage collectors: Serial (single-threaded stop-the-world), Parallel (multi-threaded for throughput), CMS (caused fragmentation and is deprecated), G1 (region-based balancing of latency and throughput with compaction), Shenandoah (reads/writes barriers, CPU-heavy scanning), ZGC (low-latency, generational design), and Epsilon (no-op collector for benchmarking). Explains that practical tuning—threads, young/old generation sizing and ergonomics—matters, and recommends choosing a collector based on desired trade-offs: latency, throughput, or memory footprint.
AI-written summary · about
chapters (8)
- 0:00Introduction to garbage collectors
- 2:53Problems without garbage collectors
- 5:21Garbage collectors origin
- 7:12Parallel garbage collectors
- 8:58CMS versus G1
- 11:30ZGC and Shenandoah
- 13:17Optimizing garbage collectors
- 14:43Modern garbage collectors benefits
related talks
52mGarbage collection for the humans
50mTrash Talk - Exploring the JVM memory management
44mGarbage Collector: How to Tame the Beast and Make It Your Best Ally
35mJava: Memory cleanup in Java 9–14
46mTrash Talk - Exploring the Memory Management in the JVM
01h 01mOpenJDK: In the new age of Concurrent Garbage Collectors
25mGarbage Collection Primer
51mTrash Talk - Exploring the JVM memory management