Mac demo performance baseline: CPU and memory
A client demo is the wrong time to discover a runaway helper, a hot export, or a memory-heavy browser session. Take a quiet system baseline before the review starts.
The short answer: open the same apps you will use in the demo, watch CPU, memory, and fan trend for about a minute, then decide whether the Mac is in its normal range. If the signal stays weird, fix it in Activity Monitor before the client joins.
A baseline is not a benchmark. It is a quick sanity check against your own normal work state. The goal is to avoid surprise, not to chase a perfect idle number.
teenystat is useful for this because it keeps CPU usage, memory usage, and fan speed visible without opening a full diagnostic app. It is still a first-pass tool. Activity Monitor remains the place for process names and quit controls.
Quick decision table
| Signal | Good enough for demo | Investigate first |
|---|---|---|
| CPU usage | Small spikes that settle while the demo app is open. | CPU stays high with no obvious workload. |
| Memory usage | Inside your normal working range for the same app set. | Memory jumps before screen sharing or the app feels stuck. |
| Fan speed | Stable or expected for a build, export, or warm room. | Fan ramps while the workload is idle. |
| Trend | Values rise, settle, and stay predictable. | Values climb every poll or keep hitting red thresholds. |
01Start from the real demo workload
Do not baseline from a blank desktop if the review will use a browser, simulator, meeting app, local server, screen recorder, and design file. Open the actual stack first. Then watch the Mac.
This matters because many demo problems are self-inflicted. A dev server may index files. A browser may restore too many tabs. A meeting app may start camera effects. A screen recorder may add system load. You want to see that before other people are waiting.
If the workload is heavy but expected, keep going. If the workload is light and the Mac is already hot or busy, stop and diagnose.
02Watch CPU, memory, and fan trend for one minute
TeenyStat polls metrics on a timer and shows the selected metric in the menu bar. Its source collects fan data when available, memory data through macOS host statistics, and CPU data through processor load information. The dashboard keeps 60 data points for CPU, memory, and fan sparklines.
For a demo baseline, the trend matters more than a single number. A momentary CPU spike when the app launches is normal. A value that keeps climbing while nothing is happening is the useful clue.
On fanless Macs, fan speed should not be part of the decision. TeenyStat detects fan availability and excludes fan speed from menu bar choices on fanless hardware.
03Use high and low values as a sanity check
The TeenyStat dashboard tracks session high and low values for fan speed, memory, and CPU usage. That is enough for a small before-demo check: did CPU spike once and settle, or did it stay near the high? Did memory land where you expected, or did opening the meeting app push the Mac into a different range?
Resetting session stats before a prep pass gives you a cleaner read. It does not create a lab-grade benchmark. It gives you one small window of evidence from the same workload you are about to show.
04Open Activity Monitor only when the signal needs names
Activity Monitor is the right tool when you need to identify a process, sort by CPU, inspect memory pressure, or quit something safely. Apple's CPU and memory guides cover those deeper views.
During a client review, though, opening a diagnostic window can derail the room. Use the menu bar for the quiet signal. Use Activity Monitor before the meeting, or when the Mac is clearly misbehaving and the review cannot continue without diagnosis.
The related guide Mac menu bar CPU monitor vs Activity Monitor covers that boundary in more detail.
05Do not turn thresholds into theater
Color-coded thresholds are helpful only when they reflect your machine and your work. TeenyStat defaults to CPU 50 and 80 percent, memory 60 and 80 percent, and fan speed 2000 and 4000 RPM. Those are starting points, not universal truth.
If your demo workload normally pushes memory to 70 percent and stays smooth, a yellow memory state may be fine. If CPU hits 80 percent while the app is idle, that is worth checking before the review starts.
Alerts should stay off unless you need them. A client demo is usually the wrong time for extra notifications.
One-minute baseline routine
- Open the meeting app, demo app, browser, local server, and screen recorder if needed.
- Reset the current high and low view if you want a fresh window.
- Watch CPU, memory, and fan trend for about one minute.
- Ignore short launch spikes that settle.
- Open Activity Monitor if CPU, memory, or fan trend stays abnormal.
- Close or quit the noisy process before the client joins.
- Leave only the one metric you care about visible during the review.
Sources checked
- TeenyStat homepage and TeenyStat Swift source for CPU reads, memory reads, fan speed reads, 3-second polling, menu bar metric selection, fanless-Mac handling, sparkline buffers, session high/low values, thresholds, and alert defaults.
- Apple Support: View CPU activity in Activity Monitor on Mac.
- Apple Support: View memory usage in Activity Monitor on Mac.
- Apple Support: View information about Mac processes in Activity Monitor.
- Apple Support: Quit an app or process in Activity Monitor on Mac.
- TeenyApps: Mac app demo checklist for client reviews.
FAQ
How do I take a Mac performance baseline before a demo?
Open the demo workload, watch CPU, memory, and fan trend for about a minute, compare against your normal range, then open Activity Monitor only if the signal stays abnormal.
What Mac metrics should I check before a client demo?
Check CPU usage, memory usage or pressure, fan speed if the Mac has fans, and whether the trend is stable before the meeting starts.
Can TeenyStat identify the process slowing down a Mac?
No. TeenyStat is a first-pass system signal. Use Activity Monitor when you need process names, columns, and quit controls.
Know the Mac is ready before the review starts.
teenystat shows CPU, memory, and fan speed in your Mac menu bar, with thresholds, sparklines, and per-core CPU detail when you need a closer look.