Check Mac CPU usage per core from the menu bar
Per-core CPU does not name the bad process. It tells you whether the Mac is busy everywhere, stuck on one narrow task, or mostly idle while something else is making the system feel slow.
The short answer: keep aggregate CPU in the menu bar if CPU spikes are a normal part of your work. Open the popover when the Mac feels wrong. If one core is hot while the rest are quiet, you are probably looking at a narrower task. If every core is busy, the whole machine is under load.
That distinction saves time. It keeps you from quitting random apps when a build is simply doing real work, and it nudges you toward Activity Monitor when a single stuck helper process is more likely. If the visible symptom is a fan that keeps running, start with the broader Mac fan troubleshooting checklist first.
teenystat shows one selected metric in the menu bar and all three vitals in the popover. For CPU, the popover includes aggregate usage, a 60-point sparkline, session high and low, and a small per-core bar chart.
Quick read
| CPU pattern | Likely meaning | Next move |
|---|---|---|
| All bars rise together | A broad workload is running: build, export, compression, indexing, or local model work. | Wait if you started it. Open Activity Monitor if you did not. |
| One or two bars stay high | A narrower thread may be stuck, busy, or single-threaded. | Check whether the foreground task explains it, then sort CPU in Activity Monitor. |
| Aggregate CPU is low | CPU is probably not the main problem. | Check memory, fan speed, disk, network, or the app itself. |
| First reading looks flat | The app is establishing a baseline between CPU tick samples. | Wait for the next polling interval before deciding. |
What per-core CPU can tell you
Aggregate CPU answers one question: how busy is the Mac overall? Per-core CPU adds a second question: is the load spread out or concentrated?
That matters because not every slow feeling has the same cause. A multi-core export can make every bar climb and still be healthy. A single stuck process can pin one core and make the system feel weird even though the average looks less dramatic. A quiet CPU with a laggy app points you somewhere else.
Treat the per-core chart as a traffic pattern. It is good at telling you which road to check next. It is not the incident report.
What TeenyStat reads
The TeenyStat source reads CPU load through macOS host_processor_info with PROCESSOR_CPU_LOAD_INFO. It collects user, system, idle, and nice ticks for each processor slot, compares the current tick counts with the previous read, and calculates each core's usage from the delta.
The first call is intentionally boring. It establishes the previous tick baseline, so the first displayed per-core values may be zero or near zero. The useful signal starts after the next read.
The app then averages the per-core values into aggregate CPU. The menu bar can show that aggregate percentage, while the popover shows the small per-core chart. TeenyStat does not label individual bars as performance cores or efficiency cores, and it does not claim to identify the process behind each bar.
When to open Activity Monitor
Open Activity Monitor when you need the process name, when CPU stays high after the task should be done, or when the menu bar number keeps disagreeing with what you expect.
Apple's Activity Monitor CPU view shows processor activity over time, system and user CPU percentages, idle percentage, and windows for current or recent processor activity. That is the right place to sort by process and decide whether to quit, wait, or investigate.
The menu bar is faster because it is visible. Activity Monitor is stronger because it is detailed. Use them in that order.
How to choose CPU thresholds
Do not set CPU alerts around a number you saw once. Spend a day watching your normal range first.
- Show CPU in the menu bar during your normal workday.
- Open the popover when a build, export, meeting app, browser tab, or background helper feels heavy.
- Set the green-to-yellow threshold above your normal working range.
- Set the red threshold where you would actually want to be interrupted.
- If the alert fires during expected work, raise the threshold or turn it off for CPU.
Threshold alerts are only useful when they point at action. A warning you ignore every day is just another notification.
Common mistakes
Reading one spike as a problem
Short spikes are normal. App launch, Spotlight, photo analysis, browser rendering, file compression, and build steps can all make CPU jump briefly. A sustained pattern matters more than a single peak.
Expecting per-core CPU to name the culprit
It will not. Per-core CPU gives shape, not identity. If you need the culprit, use Activity Monitor.
Ignoring memory and fans
A Mac can feel slow with quiet CPU if memory pressure, swap, disk, network, or app state is the real problem. Pair the CPU readout with memory and fan speed before you decide.
Sources checked
- TeenyStat claims were checked against the TeenyStat homepage and local Swift source for
CPUReader,DashboardView,CoreBarChart,DashboardViewModel, thresholds, and menu bar display. - Apple Support: View CPU activity in Activity Monitor on Mac.
- TeenyApps: Mac menu bar troubleshooting utilities to check first.
FAQ
Can per-core CPU usage identify the exact Mac app causing a slowdown?
No. It tells you the shape of the CPU load. Use Activity Monitor when you need the exact process name.
Why does the first TeenyStat CPU reading look low?
TeenyStat calculates CPU usage from tick deltas between reads, so the first read establishes a baseline and may show near-zero values.
Keep CPU, memory, and fan speed one glance away.
teenystat is a focused Mac menu bar monitor with CPU, memory, fan speed, sparklines, thresholds, and a 3-day free trial.