Runqueue latency
posts (2)
- CPU in Kubernetes from the kernel up12/12
Anatomy of a CPU problem: from an understated request to p99 latency
One incident end to end: a 500m request, no limit, no throttling, and p99 climbing from 35 to 180 ms. The whole path of the mechanism.
- CPU in Kubernetes from the kernel up10/12
How to debug CPU in Kubernetes without guessing
Usage, throttling, contention and pressure are four different phenomena. A single CPU chart settles none of them - you need an order of operations.