https://laisky.notion.site/Go-Containers-and-the-Linux-Scheduler-f4be286e0550474fbc04814bca4f43ec?pvs=4 #TIL #Golang
老生常谈了，go 不识别 cgroup 的 cpu limit，当 cgroup 给的 cpu 数目小于实际 CPU 数时，会导致 go 创建过多 threads 带来更多的切换开销。一般都会用 uber 的库 https://github.com/uber-go/automaxprocs ，加一行就完事儿：
老生常谈了，go 不识别 cgroup 的 cpu limit，当 cgroup 给的 cpu 数目小于实际 CPU 数时，会导致 go 创建过多 threads 带来更多的切换开销。一般都会用 uber 的库 https://github.com/uber-go/automaxprocs ，加一行就完事儿：
import _ "go.uber.org/automaxprocs"
Laisky on Notion
Go, Containers, and the Linux Scheduler | Notion
Like many Go developers my applications are usually deployed in containers. When running in container orchestrators it’s important to set CPU limits to ensure that the container doesn’t consume all the CPU on the host. However, the Go runtime is not aware…