Go 1.25, released in August 2025, introduced native cgroup CPU limit reading, rendering the automaxprocs library redundant for many services. While the library previously set GOMAXPROCS manually, the new runtime implementation performs this automatically. However, the library remains active if imported, overriding the runtime's native behavior and preventing dynamic updates.
The two tools handle CPU limits differently. Go 1.25 rounds up and sets a minimum of two processors to ensure the garbage collector has sufficient resources. In contrast, automaxprocs rounds down and allows a minimum of one processor. This discrepancy can lead to significant performance differences, especially for services with fractional CPU limits like 1500m.
For bursty workloads, the Go 1.25 approach of using two processors reduces tail latency by up to three times compared to the single-processor limit enforced by the library. Conversely, on steady workloads, the higher processor count can trigger CFS throttling. Developers should evaluate their load patterns before removing the library or adjusting GOMAXPROCS settings.
The runtime now updates GOMAXPROCS dynamically by periodically re-reading cgroup files, a feature disabled if the library or environment variables are present. To enable this behavior in projects using older Go versions, developers can use the godebug containermaxprocs=1 and updatemaxprocs=1 directives in their go.mod file, as the runtime behavior is tied to the go version specified there.
