go-gc performance experimental latency runtime

Go 1.25 ships experimental Green Tea garbage collector

Set GOEXPERIMENT=greenteagc at build time to test a new GC that cuts pause time 10–40% on production workloads; becoming default in Go 1.26.

Summary

Latency-sensitive services can measure real gc_duration improvements without waiting for the default switch. Early feedback shapes whether this replaces the current GC or gets reverted.

Why it matters

Latency-sensitive services can measure real gc_duration improvements without waiting for the default switch. Early feedback shapes whether this replaces the current GC or gets reverted.

Implementation verdict

Drop-in replacement via environment variable at compile time. Zero code changes required. Try it now on staging workloads; already running at Google. Risk: some workloads see no benefit—profile before committing. Worth testing immediately if you track gc overhead.

Sources

1.available by setting GOEXPERIMENT=greenteagc at build time
2.Many workloads spend around 10% less time in the garbage collector, but some workloads see a reduction of up to 40%
3.It's production-ready and already in use at Google
4.we plan to make it the default in Go 1.26

Dev Signal

Get briefs like this in your inbox — free, every weekday.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs