Thrum

What is systemstats, and why is it running on my Mac?

Last reviewed: 19 November 2026. Path, account, launchd jobs, man page and command options checked on macOS 26.3.1.

systemstats is a macOS tool that records and summarizes statistics about system power usage. One copy runs all the time as a daemon, and a second job runs it once a day for a daily task, so you may see two systemstats processes. It is part of macOS and normally uses little CPU.

systemstats at a glance

systemstats
Made byApple (part of macOS)
TypeSystem daemon and command-line tool
Location/usr/sbin/systemstats
Runs asroot
Started bylaunchd job com.apple.systemstats.analysis
Can you quit it?Not usefully. launchd restarts the daemon copy.

What is systemstats?

The man page says the systemstats command "shows a selection of statistics about system power usage." On this Mac it runs from two launchd jobs: com.apple.systemstats.analysis starts systemstats --daemon at boot and keeps it running, and com.apple.systemstats.daily starts systemstats --daily every day at 00:15.

Its --help output lists commands for working with the stats files it keeps in a local system store, including --list-files, --show-events, --dump and --create-archive, plus a deprecated --dashboard that shows "a selection of statistics about the system's power usage over the sample range."

Is systemstats safe?

Yes. It is in /usr/sbin on the read-only system volume and runs as root. Two copies is normal on macOS 26.

Why does systemstats use so much CPU and disk?

How much CPU is normal for systemstats?

Low CPU, usually under 1%, from the daemon copy, and a short burst when the daily job runs. A few megabytes of memory per copy.

How do you stop systemstats from using so much CPU?

  1. Check which copy is busy. Run ps -axo pid,%cpu,command | grep systemstats. The --daemon copy runs all the time; a busy --daily copy is the once-a-day task and will finish.
  2. Let the daily task finish. If the daily copy is running, leave it; it exits when done.
  3. Restart if the daemon stays high. Sustained high CPU from the --daemon copy is unusual. A restart starts it fresh.

When should you worry about systemstats?

Constant high CPU from systemstats for hours is not expected. Note which copy it is and restart.

A systemstats outside /usr/sbin would not be Apple's.

How do you check systemstats in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type systemstats in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every systemstats process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password.

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'systemstats' | grep -v grep
sudo fs_usage -w -f filesys systemstats

How can Thrum help with systemstats?

Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when systemstats is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.

Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.

Questions about systemstats

Why are there two systemstats processes?

One is the always-running daemon started by com.apple.systemstats.analysis, and the other is the daily task started by com.apple.systemstats.daily.

Can I use systemstats to see power usage?

Yes, as root. sudo systemstats --show-events prints recorded events, and systemstats --help lists the options. Its dashboard view still exists but is marked deprecated.

Sources