What is sysmond, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
sysmond is the macOS system monitor daemon. launchd starts it on demand when a program connects to its service, it gathers system and per-process statistics as root, and it exits when it has been idle for a while. Its CPU use rises while a monitoring tool is asking it for data frequently.
sysmond at a glance
| sysmond | |
|---|---|
| Made by | Apple (part of macOS) |
| Type | System daemon |
| Location | /usr/libexec/sysmond |
| Runs as | root |
| Started by | launchd job com.apple.sysmond |
| Can you quit it? | Yes, but launchd starts it again when a client asks for data. |
What is sysmond?
The man page describes sysmond as the "system monitor daemon" and says only that it "should not be run directly." Its launchd job, com.apple.sysmond, registers a Mach service of the same name and lets launchd end it when idle; on this Mac launchd recorded that it was last started by an IPC request and last exited as idle.
Apple does not document which programs use it. Its binary contains object types named for processes, coalitions (groups of related processes) and system rows, and Activity Monitor links against a system library called libsysmon. Because it runs as root, it can read statistics about every process, which an ordinary app cannot.
Is sysmond safe?
Yes. It is part of macOS in /usr/libexec on the read-only system volume. It only reads statistics; it does not change processes.
Why does sysmond use so much CPU and memory?
- A monitoring app asking for data. Collecting statistics for every process is real work. A tool that requests them every second keeps sysmond busy for as long as it is open.
- Many processes. The more processes are running, the more there is to collect on each request.
- Started on demand. It is launched when a client connects and can be ended when idle, so it appears and disappears. About 3.5 MB was observed on this Mac.
How much CPU is normal for sysmond?
Not running, or near 0% CPU, when nothing is monitoring the system. A few percent CPU while a monitoring tool with a fast update interval is open is in the expected range.
How do you stop sysmond from using so much CPU?
- Close monitoring tools you are not looking at. Quit Activity Monitor or other system monitors when you do not need them.
- Slow the update interval. In Activity Monitor, choose View > Update Frequency and pick a longer interval so data is requested less often.
- Let it exit. Once nothing is asking for data, launchd lets sysmond exit on its own.
When should you worry about sysmond?
sysmond busy with no monitoring app open suggests some background tool is polling system statistics; quit menu bar utilities one at a time to find it.
A sysmond outside /usr/libexec would not be Apple's.
How do you check sysmond in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type sysmond in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every sysmond process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'sysmond' | grep -v grep
How can Thrum help with sysmond?
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 sysmond 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 sysmond
Why does sysmond appear when I open Activity Monitor?
Apple does not document the connection, but Activity Monitor links against the libsysmon library, and sysmond is started on demand when a client connects to its service.
Can I disable sysmond?
No supported setting does, and it only runs when something asks it for data.
Sources
- sysmond(8) man page: run man sysmond in Terminal
- Apple Support: Change how often information is updated in Activity Monitor on Mac