Monitoring CPU usage makes it easier to explain sluggish applications, stuttering desktops, and overloaded Windows servers. Task Manager and Resource Monitor offer quick snapshots, but short spikes and intermittent slowdowns often need a longer capture to diagnose. Consistent CPU baselines also support capacity planning before the next incident report arrives with dramatic punctuation.
Performance Monitor (PerfMon) reads performance counters exposed by the operating system and displays them as live graphs. The Performance Monitor view is suited for real-time observation, while Data Collector Sets record the same counters to log files (such as .blg or .csv) for later review under Reports.
Counter selection and sampling frequency affect both accuracy and overhead. Using Processor counters shows overall load, while Process counters isolate a specific executable, and a small sample interval can generate large logs quickly. Creating or starting a data collector set typically requires administrative rights, and utilization counters do not replace hardware telemetry such as temperatures.
_Total shows combined usage across all logical CPUs, while individual instances (0, 1, …) isolate a single core.
Process → % Processor Time isolates CPU for a single executable, and values can exceed 100 on multi-core systems.
Intervals like 5 to 15 seconds are typical for troubleshooting without producing oversized logs.
High-frequency sampling can grow log files quickly, and a full system drive can disrupt updates, logins, and crash dumps.
Collection runs in the background until stopped, and the status shows Running while active.