STW | BestHub

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.

DubboJVMSTW

0 likes · 9 min read

Understanding Thread Pool Exhaustion in Dubbo: Causes and Diagnosis

Qunar Tech Salon

Oct 21, 2022 · Backend Development

Root Cause Analysis and ZGC Optimization for a High‑Concurrency Ticket Pricing Service

This article details the investigation of a 2% timeout rate in a billion‑request‑per‑day ticket pricing service, identifies GC‑induced stop‑the‑world pauses as the main cause, and demonstrates how switching from ParNew+CMS to G1 and finally to ZGC dramatically reduces latency and timeout rates.

DubboGarbage CollectionJava

0 likes · 24 min read

Root Cause Analysis and ZGC Optimization for a High‑Concurrency Ticket Pricing Service

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 MarkingG1

0 likes · 11 min read

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

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 CollectionGoMark and Sweep

0 likes · 31 min read

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