Computer Science
posts (5)
- 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 up8/12
Why 1 CPU does not mean one core
CPU time and CPU placement are two different mechanisms. A limit says how much you may consume; affinity and cpuset say where a task may execute.
- 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.
- CPU in Kubernetes from the kernel up2/12
cgroups and CPU: how Linux splits the processor between groups of processes
Group scheduling, cpu.weight and hierarchy - how the kernel divides CPU between groups of processes instead of individual tasks.
- CPU in Kubernetes from the kernel up1/12
How Linux really gives a process CPU
A process does not "have CPU". It is ready to run, and the scheduler decides when it actually gets processor time.