How Go 1.25 Changes GOMAXPROCS in Containers

A Go container can be limited to one CPU while the runtime sees all 32 logical CPUs on its node. Before Go 1.25, the runtime could schedule work as if all 32 were available. When a burst of CPU-bound work used the container’s quota, Linux could pause the whole container until its quota renewed. Requests that were ready to run then waited, which can show up as latency spikes under load. ...

January 13, 2025 · 5 min