Descriptions:
Dave Plummer, a retired Microsoft operating systems engineer who personally wrote the original Windows Task Manager code, pulls back the curtain on how CPU usage percentages are actually calculated — and why they are, in his words, “a useful lie built from a pile of true counters.” Using Microsoft’s own source code, he walks through the timer-driven refresh architecture, explaining why Task Manager functions more like an odometer than a speedometer.
The core insight is in how the denominator is constructed: rather than dividing by a fixed timer interval (which would introduce errors whenever the UI thread is delayed), Task Manager sums the cumulative CPU time consumed by every process across the entire system and uses that delta as the denominator. This makes the per-process percentage a ratio of actual consumed time rather than an assumed elapsed wall-clock window — a subtle but important distinction that keeps the numbers meaningful even when the refresh timer fires late.
Plummer also recounts a personal debugging story involving a rare edge case where CPU usage would briefly exceed 100%, how he instrumented the code with assert statements that included his home phone number to crowdsource detection across Microsoft’s internal dogfood users, and the anticlimactic resolution after the Windows beta shipped to thousands. For anyone who has ever glanced at Task Manager and wondered why the numbers feel inconsistent under load, this video provides the definitive technical explanation straight from the original author.
📺 Source: Dave’s Garage · Published April 18, 2026
🏷️ Format: Deep Dive
