Get the latest tech news
Go Production Performance Gotcha – GOMAXPROCS
Learn how to solve unexpected performance issues in Go applications by correctly configuring the GOMAXPROCS parameter for optimal CPU usage in containers
This deamonset creates a pod on each host called the node-agent which collects information about workloads and sends it out of the cluster to be stored. In our case we have a default cpu limit on the node-agent of a single core so that we don’t impact customer workloads. We’re always running in k8s so we decided to use the downwards api to set the GOMAXPROCS environment variable on the node-agent container at deployment time.
Or read this on Hacker News
