hard20 pts · first answer countskuberneteslinux-performance

Throttled but not busy

A multithreaded service in a Kubernetes pod with a CPU limit of 1 core shows only 40% average CPU usage, but p99 latency is high and the container_cpu_cfs_throttled_periods_total metric keeps rising. What is the most likely cause?

A.The node is out of memory and swappingB.The readiness probe is failingC.The CPU request is too high, so the scheduler gives it less CPUD.The CFS quota is enforced per 100 ms period; bursts across many threads use up the quota early in the period and the container is paused until the next period

← Tail latency with fan-out Handling overload →