01 · Why it’s true
A CPU core runs one thread at a time. The kernel’s scheduler keeps runnable threads queued and switches between them many times a second, giving each a slice of time, so it looks like everything runs at once.
When there are more runnable threads than cores, the extras wait in a run queue. That waiting doesn’t show up as extra CPU usage (which can’t go past 100%), but it does show up as latency. On Linux, the load average counts runnable threads plus threads in uninterruptible sleep, which is usually waiting on disk I/O.
02 · Picture it
03 · In the interview
- “The box is slow”: telling CPU saturation (long run queue) apart from I/O waiting.
- Reading load average relative to the number of cores.
- Recognizing CPU throttling in containers when a CPU limit is hit.
04 · Practice question
“A 4-core server has a load average of 16, but CPU usage is only 30%. What’s going on?”
A strong answer covers
- On Linux, load average includes threads in uninterruptible sleep — usually waiting on disk or network storage — not just threads wanting CPU.
- High load with low CPU suggests lots of threads blocked on I/O rather than CPU contention.
- Check
vmstat(thebcolumn andwa),iostat -xfor device latency and utilization, and look for processes inDstate. - Likely causes: a slow or saturated disk, a hung network filesystem, or heavy swapping.