Tagged articles
G1 GC
31 articles · Page 1 of 1
This article explains how frequent G1 Mixed GC pauses, not Redis slowness, cause distributed lock waits by stalling lock-holding threads, and details a six-step troubleshooting process linking GC logs, business logs, and heap analysis to identify large objects, compensation tasks, and unbounded local caches as root causes.
Distributed LocksG1 GCHumongous Objects
0 likes · 19 min read

JDK 27 introduces nine JEPs including G1 as universal default GC, 64-bit compact object headers cutting heap usage 25%, default post-quantum TLS 1.3 key exchange, plus preview features like lazy constants, primitive pattern matching, structured concurrency, and Vector API for AI acceleration.
G1 GCJDK 27Java 27
0 likes · 22 min read

JDK 27 introduces three major default behavior changes—G1 as universal garbage collector, 64-bit compact object headers reducing heap usage by 25%, and post-quantum hybrid key exchange for TLS 1.3—plus preview features like structured concurrency, lazy constants, primitive pattern matching, and Vector API for AI workloads.
G1 GCJDK 27Lazy Constants
0 likes · 22 min read

JDK 27 delivers nine JEPs including G1 as universal default GC, compact object headers cutting heap usage by 25%, post-quantum TLS 1.3 enabled by default, plus preview features like lazy constants, primitive pattern matching, structured concurrency, and Vector API for AI workloads.
G1 GCJDK 27JVM Performance
0 likes · 19 min read


java1234Sep 17, 2026 · Backend Development
Java 27 introduces four final features: G1 becomes the universal default garbage collector, compact object headers reduce memory overhead by 4 bytes per object, TLS 1.3 adds post-quantum hybrid key exchange by default, and JFR automatically redacts sensitive data like passwords and tokens before recording.
G1 GCJFR redactionJava 27
0 likes · 18 min read

JDK 27 introduces nine JEPs including G1 as universal default GC, compact object headers reducing heap usage by 25%, and post-quantum TLS 1.3 hybrid key exchange enabled by default — all requiring zero code changes — plus preview features like lazy constants, primitive pattern matching, structured concurrency, and Vector API for AI workloads.
G1 GCJDK 27JFR
0 likes · 22 min read

This article explains why fixing G1's young generation size with -Xmn or percentage flags often harms performance, and demonstrates how to tune young GC by analyzing pause targets, Eden sizing, TLAB/PLAB logs, and object promotion patterns to let G1's adaptive sizing balance throughput and latency.
G1 GCGC LogsJava performance
0 likes · 16 min read

JDK 27 introduces nine JEPs, highlighted by G1 GC becoming the universal default, compact object headers cutting heap memory by 22%, post-quantum TLS 1.3 key exchange, JFR data redaction for compliance, and structured concurrency reaching its seventh preview, delivering immediate performance gains and future-proof security for Java applications.
G1 GCJDK 27JFR
0 likes · 11 min read

This article teaches how to analyze G1 GC logs beyond simple pause times by breaking down phase timings, heap changes, GC causes, and concurrent marking overhead, then mapping log signals like high Update RS or Object Copy to concrete code-level issues such as excessive reference writes, humongous allocations, or weak reference abuse.
G1 GCGC LogsGarbage Collection
0 likes · 27 min read

This comprehensive guide covers JVM garbage collection from fundamentals to advanced tuning, explaining reference counting vs reachability analysis, four GC algorithms, six collectors (Serial, Parallel, CMS, G1, ZGC, Shenandoah), G1 internals (Region, RSet, SATB, Mixed GC), ZGC's colored pointers and concurrent compaction, GC tuning methodology with parameters, and JDK 17 Graal JIT optimizations.
G1 GCGC TuningGarbage Collection
0 likes · 72 min read

Mixed GC in G1 only reclaims a portion of the Old generation that fits within the pause‑time budget, so seeing the Old region size stay high after a mixed pause does not mean G1 has failed, but rather reflects collection cost, survival rates, and budgeting constraints.
G1 GCGarbage CollectionJVM
0 likes · 16 min read

JDK 27 changes the default garbage collector from a resource‑aware Serial GC to G1, which can unexpectedly increase CPU usage, alter latency and throughput for small‑container Java services even when no code or JVM flags are changed, so teams must verify the GC in use and benchmark both collectors under realistic limits.
ContainerizationG1 GCGarbage Collection
0 likes · 22 min read

A production outage at 3 am revealed a 10‑second Full GC pause on an 8 GB heap; the article walks through evidence collection, heap‑size rebalancing, switching to G1, fine‑tuning G1 parameters, and code changes that together reduced Full GC pauses to 200 ms and improved latency dramatically.
Full GCG1 GCGC Tuning
0 likes · 12 min read


java1234May 19, 2026 · Backend Development
JDK 26 introduces a suite of impactful JEPs—including primitive type pattern matching, G1 GC throughput gains, AOT object caching for faster startup, built‑in PEM encoding, stricter final‑field handling, HTTP/3 support, LazyConstant, structured concurrency, and a mature Vector API—each backed by code examples and performance data to help developers modernize their Java applications.
G1 GCJDK 26Java
0 likes · 29 min read

The article explains how Java’s six‑month release cadence has led to JDK 26’s major upgrades—including HTTP/3, Structured Concurrency, stronger final‑field immutability, AOT object caching, G1 GC enhancements, Lazy Constants, pattern‑matching extensions, Vector API and PEM support—showing the performance, latency and security gains developers can unlock by moving beyond Java 8.
G1 GCHTTP/3JDK 26
0 likes · 9 min read

Oracle’s JDK 26, a non‑LTS release, delivers dramatic gains—15% higher G1 GC throughput, up to 50% lower latency, 40‑60% memory reduction via Valhalla value classes, native HTTP/3 support, AOT cache for all GCs, and enhanced security—offering developers faster startup, lower costs, and safer code.
G1 GCHTTP/3JDK 26
0 likes · 10 min read

JDK 26, released on March 17, 2026, introduces structured concurrency, native HTTP/3, primitive‑type pattern matching, lazy constants, G1 GC sync improvements, AOT object caching, final‑field reflection limits and post‑quantum encryption, delivering up to 30% performance gains, 40% thread‑utilisation, and up to 70% code‑size reduction without requiring code changes or new dependencies.
G1 GCHTTP/3JDK 26
0 likes · 11 min read

This guide walks you through practical performance tuning of Tomcat 11 on JDK 21, covering JVM memory settings, GC selection, connector and thread‑pool optimization, virtual‑thread integration, benchmark scripts, security hardening, high‑availability deployment, and comprehensive monitoring and troubleshooting techniques.
G1 GCJDK21JVM
0 likes · 51 min read

This article explains the core concepts of the G1 garbage collector, including its memory management duties, heap region types and sizing, pause‑time prediction model, card table and bitmap usage, object header structure, and both fast and slow object allocation strategies.
G1 GCGarbage CollectionHeap Regions
0 likes · 9 min read

The G1 Garbage Collector, introduced in Java 7 update 4, replaces CMS by using a region‑based design that minimizes pause times and improves throughput, and a detailed video with diagrams and code examples is provided to deepen understanding of its operation.
G1 GCGarbage CollectionJVM
0 likes · 2 min read

This article dives deep into the OpenJDK G1 FullGC implementation, explaining its architecture, trigger conditions, preparation steps, and the four‑phase collection process while comparing single‑threaded and multi‑threaded implementations in JDK 8 and JDK 11, and highlighting code paths that can cause long GC pauses.
FullGCG1 GCGarbage Collection
0 likes · 18 min read


21CTOFeb 5, 2022 · Fundamentals
This article explains the JEP 423 proposal to fix regions in the G1 garbage collector, allowing Java threads to avoid pauses during JNI critical sections and reducing GC latency, while discussing implementation details, potential heap exhaustion risks, and upcoming JDK release timelines.
G1 GCGarbage CollectionJEP 423
0 likes · 5 min read

This tutorial demonstrates how to create a Micronaut microservice, compile it into a GraalVM Native Image, and apply advanced optimizations such as G1 GC, profile‑guided compilation, and UPX packing to achieve faster startup, lower memory usage, and higher throughput in cloud environments.
G1 GCGraalVMJava
0 likes · 21 min read

This article explains the G1 garbage collector’s architecture, region types, pause‑time prediction model, memory allocation parameters, collection phases, and tuning considerations, providing code examples and practical insights to improve performance for Java developers.
G1 GCGarbage CollectionJVM
0 likes · 11 min read

This article explains the different types of Java garbage collectors, focuses on the G1 (Garbage‑First) collector’s region‑based architecture, key data structures and algorithms such as TLAB, PLAB, CSet, Card Table, RSet, and SATB, and provides detailed log analysis and tuning recommendations to improve pause times and throughput.
G1 GCGarbage CollectionJVM
0 likes · 37 min read

This article explains Java HotSpot VM garbage‑collection ergonomics, detailing pause‑time and throughput goals, generational collection mechanics, default heap sizing, and how to select and tune Serial, Parallel, G1, and ZGC collectors for optimal performance.
G1 GCGC ErgonomicsGarbage Collection
0 likes · 32 min read

This article explains why the CMS garbage collector was removed in JDK 9, shows the deprecation warning, and evaluates three migration paths—switching to G1 GC, adopting ZGC, or continuing with CMS—helping developers choose the best option for their applications.
CMS GCG1 GCGarbage Collection
0 likes · 5 min read

This article provides a comprehensive overview of the G1 (Garbage First) collector, covering its region-based memory layout, cross‑generation reference handling, SATB write barriers, various GC phases (Young, Mixed, Full), and how to interpret detailed G1 GC logs for performance tuning.
G1 GCGarbage CollectionJVM
0 likes · 16 min read

This article explains the G1 (Garbage‑First) garbage collector introduced in JDK7, its region‑based architecture, key differences from CMS, and the complete GC cycle—including Young GC, concurrent phases, mixed GC, and Full GC—while providing real‑world log examples and performance insights for Java developers.
G1 GCGC LogsGarbage Collection
0 likes · 10 min read

This article walks through the G1 garbage collector’s heap structure, region‑based allocation, young‑generation collection steps, and the detailed phases of old‑generation collection, providing clear diagrams and practical insights for Java developers.
G1 GCGarbage CollectionHeap Regions
0 likes · 9 min read

The G1 Garbage‑First collector is a server‑side, region‑based Java GC designed for multi‑processor, large‑memory systems that concurrently marks objects using SATB, tracks cross‑region references with RSets, and employs a pause‑prediction model to meet user‑specified pause‑time goals while maintaining high throughput.
G1 GCGarbage CollectionJVM
0 likes · 15 min read
