Performance Engineering
posts (4)
- 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 up9/12
NUMA, SMT and cache: when hardware topology starts to matter
Two workloads can get the same CPU time and do different amounts of work. This is where the CPU abstraction ends and the physics of the machine begins.
- CPU in Kubernetes from the kernel up5/12
CPU Contention: when a process wants CPU and does not get it
With no limit at all a process can sit and wait. All it takes is runnable demand exceeding available capacity - and you only see it in latency.
- series · 12 parts
CPU in Kubernetes from the kernel up
A CPU model built bottom-up: from runnable tasks and the scheduler, through cgroups, requests and limits, to throttling, contention, PSI and diagnostics.