Feature · 負荷
Why the battery is dropping:CPU, GPU, memory, disk.
CPU, GPU, memory pressure, and disk I/O, right beside your battery numbers. When the battery drains fast, one of these four usually explains it: a pinned core, a busy GPU, a sync client writing all afternoon.
Why it matters
“It died fast today” is a feeling. Load is evidence. The system panel shows that something is working your Mac; the app energy panel names it. Together they turn a bad battery day into a process you can quit.
Why load belongs next to battery
Battery drain is downstream of work. A Mac at 4% CPU and a Mac at 85% CPU are different machines in runtime terms, and the difference is usually one process you forgot about. System load puts the four readings that matter (CPU, GPU, memory pressure, disk I/O) beside the battery numbers rather than in a separate app.
What each reading tells you
- CPU. The single best predictor of discharge rate. A single runaway thread pinning one core shows up here long before the battery percentage reacts.
- GPU. Often the real culprit on Apple Silicon: video calls, WebGL, and hardware-accelerated scrolling all land here rather than on the CPU.
- Memory pressure. High pressure means compression and swap, and swap means disk writes, an indirect but real battery cost.
- Disk I/O. Sustained writes are the signature of a backup, a sync client, or a Spotlight reindex quietly running.
Load, then blame
System load tells you that something is working the machine; the app energy panel tells you what. Together they turn “my battery died fast today” into a process name you can quit. If the load is sustained and thermal, see thermal throttling for what the Mac does about it.
Frequently asked.
- Isn’t this just Activity Monitor?
- The readings come from the same system sources, but they sit beside your battery numbers instead of in a separate window, and Sensei keeps a short history so you can see whether a spike is new or constant.
- Does sampling this drain the battery?
- The sampler is deliberately light: a periodic read of counters the OS already maintains, with no polling loop tighter than the app’s own refresh tick.
- What is memory pressure, exactly?
- It’s macOS’s own measure of how hard the memory subsystem is working: closer to “how much compressing and swapping is happening” than to “how much RAM is used”. High pressure costs battery; high usage alone doesn’t.