Tag

write barrier

0 views collected around this technical thread.

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 CollectionGoMark and Sweep
0 likes · 31 min read
Evolution of Garbage Collection in Go: From Mark‑Sweep to Hybrid Write Barriers
Ops Development Stories
Ops Development Stories
Aug 16, 2021 · Fundamentals

Tri-Color Marking Explained: Avoid GC Mis‑marks and Boost Java Performance

This article introduces the tri‑color marking algorithm used in Java garbage collectors, detailing the roles of white, gray, and black objects, the marking process, common pitfalls like mis‑marks, and solutions such as incremental updates and snapshot‑at‑the‑beginning techniques.

Garbage CollectionJavaSTAB
0 likes · 11 min read
Tri-Color Marking Explained: Avoid GC Mis‑marks and Boost Java Performance
Tencent Cloud Developer
Tencent Cloud Developer
Aug 4, 2021 · Fundamentals

Golang Garbage Collection: Algorithms, Memory Management, and Evolution

The article details Go’s runtime memory architecture—including pages, spans, mcache, and size classes—and explains its non‑generational concurrent tri‑color mark‑and‑sweep garbage collector, the required write‑barrier techniques, and the collector’s evolution, phases, trigger mechanisms, and practical code examples across Go 1.0‑1.16.

Concurrent MarkingGarbage CollectionGo
0 likes · 30 min read
Golang Garbage Collection: Algorithms, Memory Management, and Evolution
High Availability Architecture
High Availability Architecture
Aug 13, 2019 · Fundamentals

In‑Depth Study of Go’s Garbage Collection Algorithm and Its Evolution

This article provides a comprehensive analysis of Go’s non‑generational concurrent mark‑and‑sweep garbage collector, tracing its evolution from early stop‑the‑world implementations to the mixed write‑barrier design in Go 1.8, and explains how to interpret GC traces, tune GC parameters, and reduce latency caused by mark‑assist and STW pauses.

Concurrent Mark and SweepGarbage CollectionGo
0 likes · 22 min read
In‑Depth Study of Go’s Garbage Collection Algorithm and Its Evolution