GOMAXPROCS, CPU Limits, and the Kubernetes Trap That Silently Kills Go Throughput
If your Go pod has less than one full core, the runtime treats it as single-threaded for parallelism. For years the Go scheduler didn't know about Kubernetes CPU limits and over-scheduled anyway. Here's what changed in Go 1.25, why giving a pod 'extra' CPU sometimes dramatically improves throughput, and how to get it right in 2026.