automaxprocs now costs your Go binary a CPU
https://medium.com/@omlahore47/automaxprocs-now-costs-your-go-binary-a-cpu-61d63a12e3ec
Since the past eight years, if you ever found that your Go service was getting throttled inside Kubernetes, the way to fix that was using one import. And with the release of Go 1.25, that same job was absorbed into the runtime itself. But that import is still sitting in your go.mod file, and it is now taking a CPU away from you.
https://medium.com/@omlahore47/automaxprocs-now-costs-your-go-binary-a-cpu-61d63a12e3ec