Thrum

What is logd, and why is it using CPU on my Mac?

Last reviewed: 19 November 2026. Path, account, launchd job, man page and log store size checked on macOS 26.3.1.

logd is the daemon at the centre of the macOS unified logging system: every process writes log messages into memory it shares with logd, and logd compresses them and keeps them in a ring buffer or on disk. Its CPU and disk use rise when apps log a lot, for example when one is stuck in an error loop. It is part of macOS and must keep running.

logd at a glance

logd
Made byApple (part of macOS, unified logging)
TypeSystem daemon
Location/usr/libexec/logd
Runs asroot
Started bylaunchd job com.apple.logd
Can you quit it?No. Log messages from every process depend on it, and launchd restarts it.

What is logd?

According to its man page, logd "is responsible for handling and managing historical data and related metadata." All processes that use os_log "share pages of memory with logd and append entries to them. logd reads pages and combines and compresses this data. Depending on configured policies, it keeps them in a local ring buffer or writes them out to persistent storage." The log command and the Console app read that data through logd.

Apple's developer documentation says the unified logging system "centralizes the storage of log data in memory and on disk, rather than writing that data to a text-based log file." On this Mac the persistent store in /var/db/diagnostics was about 1.6 GB. logd runs as root from the com.apple.logd launchd job.

Is logd safe?

Yes. logd is part of macOS in /usr/libexec on the read-only system volume. It is one of the processes that is always running.

Why does logd use so much CPU, disk and memory?

How much CPU is normal for logd?

A few percent CPU or less, rising briefly during busy moments such as startup or app launches. Steady disk writes at a low rate are normal.

Sustained double-digit CPU means something is logging far more than usual.

How do you stop logd from using so much CPU?

  1. Find the process that logs the most. Run log show --last 1m --style compact | awk '{sub(/\[.*/,"",$4); print $4}' | sort | uniq -c | sort -rn | head in Terminal. It counts messages per process over the last minute; the top names are the busiest loggers.
  2. Watch one suspect live. Run log stream --process NAME with the process name to see what it is repeating. Press Control-C to stop.
  3. Fix or quit the noisy app. Repeated error messages usually point to a problem the app can recover from after a restart or an update. Quit it, update it, or remove it.
  4. Turn off extra logging you enabled. If you or a developer turned on debug logging for a subsystem with log config, turn it back off. Debug-level logging is far more voluminous.
  5. Close live log viewers. Pausing Console's live stream reduces work for logd and diagnosticd.

When should you worry about logd?

logd above about 10% CPU for a long time is worth investigating with the first step above; the cause is almost always another process that logs too much.

Do not delete files in /var/db/diagnostics by hand. macOS manages the size of the store itself.

How do you check logd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type logd in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. 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 logd 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 'logd' | grep -v grep
sudo fs_usage -w -f filesys logd

How can Thrum help with logd?

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 logd 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 logd

Where does macOS store logs?

The unified log is kept in a compressed store in /var/db/diagnostics (with supporting data in /var/db/uuidtext), not in text files. Use Console or the log command to read it.

Can I turn off logging to reduce logd's CPU?

No supported setting turns off unified logging for the whole Mac. Fixing the process that logs too much is the effective fix.

What is the difference between logd and syslogd?

logd runs the modern unified logging system. syslogd is the older Apple System Log server that still receives messages sent through the classic syslog and ASL interfaces.

Sources