← Monday, October 5, 2026Performance & OSDeep dive
Swapped Go GC metadata can turn a collection into a 40 ms pause
Go’s garbage collector reads metadata outside the heap during a stop-the-world pause; if that metadata is swapped out, the collector can stall on page faults. Engineers running memory-heavy Go services should account for swap and GC metadata when diagnosing latency.
- What
- A Go garbage collector pause reached 40 ms when GC metadata was in swap.
- How
- During the worst pause, 39 ms went to 228 page faults while the stopped-the-world collector read metadata.
- Why it matters
- Engineers using swap to absorb memory spikes should account for GC metadata faults, which can stall all Go processes in the cgroup.
Read on frn.sh → Hacker News · 32 comments
Discussion
Discussion is not switched on yet. Use Note above to keep your own thoughts on this story.
Headline, summary, brief and diagram are written by a model from the source's own text; the link, byline and numbers come from the source. Read the original before relying on a claim.