How to find CPU-heavy processes

Watch a time window

Opening an app, rendering a page, indexing files, and installing an update can briefly use substantial CPU. Sample for at least a minute and look for sustained load or repeated peaks that match the slowdown.

Read percentages correctly

Process CPU and whole-system CPU may use different scales on multicore systems. Compare processes against one another and use a normalized system gauge for overall load.

Check the process identity

1. Confirm the app or service name and owner.
2. Save work in the related app.
3. Try the app’s normal Quit command first.
4. Force quit only if it is unresponsive and you understand the impact.

Find repeat offenders

A single snapshot can mislead. MemoryPilot combines CPU and memory impact, makes the sorted column explicit, and preserves a live timeline so recurring offenders stand out.