BestHub
Sign in
Tagged articles

STW

5 articles · Page 1 of 1
Su San Talks Tech
Su San Talks Tech
Apr 22, 2024 · Fundamentals

Why Java’s Object Graph Traversal Pauses: Tri‑Color Marking & STW Solutions

This article explains the two‑phase reachability analysis in Java garbage collection, detailing why the object‑graph traversal stage incurs stop‑the‑world pauses, how the tri‑color marking model reveals issues like floating garbage and object disappearance, and describes incremental update and snapshot‑at‑the‑beginning techniques that avoid STW.

Garbage CollectionJavaSATB
0 likes · 14 min read
Why Java’s Object Graph Traversal Pauses: Tri‑Color Marking & STW Solutions
DeWu Technology
DeWu Technology
Feb 23, 2024 · Backend Development

Understanding Thread Pool Exhaustion in Dubbo: Causes and Diagnosis

The article explains that Dubbo’s zero‑capacity SynchronousQueue causes a thread‑pool “EXHAUSTED” error when incoming requests outpace consumption, often triggered by slow DB queries, lock contention, or network jitter, and that JVM stop‑the‑world pauses fill the OS TCP receive buffer, creating a post‑pause traffic burst that overwhelms the pool, with diagnostics using safepoint statistics.

DubboJVMNetwork
0 likes · 9 min read
Understanding Thread Pool Exhaustion in Dubbo: Causes and Diagnosis
Sanyou's Java Diary
Sanyou's Java Diary
Feb 22, 2022 · Backend Development

Understanding CMS and G1 Garbage Collection: Strategies, STW, and Performance Trade‑offs

This article explains the inner workings of Java's CMS and G1 garbage collectors, detailing their four-phase processes, the need for stop‑the‑world pauses, strategies like incremental update and SATB to handle missed marks, and compares their advantages, drawbacks, and suitable replacement scenarios.

CMSConcurrent MarkingGarbage Collection
0 likes · 11 min read
Understanding CMS and G1 Garbage Collection: Strategies, STW, and Performance Trade‑offs
Xueersi Online School Tech Team
Xueersi Online School Tech Team
Dec 24, 2021 · Fundamentals

Evolution of Garbage Collection in Go: From Mark‑Sweep to Hybrid Write Barriers

This article explains how Go's garbage collection has progressed from the simple stop‑the‑world mark‑and‑sweep algorithm in Go 1.3, through the tri‑color concurrent marking with insert and delete write barriers in Go 1.5, to the hybrid write‑barrier approach introduced in Go 1.8 that dramatically reduces pause times while preserving memory safety.

Garbage CollectionMark-and-SweepSTW
0 likes · 31 min read
Evolution of Garbage Collection in Go: From Mark‑Sweep to Hybrid Write Barriers