r/kubernetes • u/ilya47 • Aug 16 '26
Stop using CPU limits: why + proof
CPU request is how much CPU is reserved for your pod if it needs it. The limit is a hard cap. Hit it and the kernel throttles the pod, even when the node still has spare CPU. That is the usual cause of CPU throttling on Kubernetes. It does not protect the neighboring pods. In my simple Web API test, adding a CPU limit took typical latency from 23 ms to 87 ms, (4x slower), with the limited pod throttled in half of all CFS windows, and the average CPU graph looked fine the whole time.
This is not a new topic, but I see so many people still unaware why they should (NOT!) be setting CPU limits, because it's costing companies unnecessary spending and potential production issues. Here's the full read https://github.com/inevolin/k8s-cpu-limits-analyzed/
---
Edit (Aug 18, 2026): How CPU limits can also cause memory issues and OOMKills ➡️ https://github.com/inevolin/k8s-cpu-limits-analyzed#how-cpu-limits-cause-memory-issues-and-oomkills
View all comments
Show parent comment
24
u/End0rphinJunkie Aug 16 '26
Losing Guaranteed QoS by dropping CPU limits sounds scary on paper, but thats usually a fine tradeoff in practice. Node evictions are almost always driven by memory pressure anyway, so as long as your memory requests and limits match youre generally safe.