What is PerfPowerServices, 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.
PerfPowerServices is the macOS daemon that manages structured log archives from which system power and performance data can be retrieved. It records and stores that data continuously, so it shows small, steady activity and occasional bursts when it writes or tidies its archives. It is part of macOS and launchd keeps it running.
PerfPowerServices at a glance
| PerfPowerServices | |
|---|---|
| Made by | Apple (part of macOS, power and performance logging) |
| Type | System daemon |
| Location | /usr/libexec/PerfPowerServices |
| Runs as | root |
| Started by | launchd job com.apple.PerfPowerServices |
| Can you quit it? | Not usefully. launchd keeps it running. |
What is PerfPowerServices?
The man page says PerfPowerServices "manages structured log archives that enable retrieval of system power and performance data" and that it "works only within the context of a launchd job and should not be run from the command line." Its launchd job, com.apple.PerfPowerServices, keeps it alive at all times and registers services named com.apple.powerlog_mover and com.apple.powerlog.plxpclogger.xpc, which tie it to what macOS calls the power log.
Apple does not document which features read these archives, so this page does not name them. What can be checked is that it runs as root, that launchd restarts it if it exits, and that it is present on every Mac.
Is PerfPowerServices safe?
Yes. It is part of macOS in /usr/libexec on the read-only system volume and is signed by Apple.
Why does PerfPowerServices use so much CPU, disk and memory?
- Recording power and performance events. Other parts of macOS log power and performance data to it throughout the day, so it is rarely completely idle.
- Writing and moving archives. Archiving recorded data writes to disk; the
powerlog_moverservice name points to moving those archives. - Buffered data. Recent data is held in memory before it is written. About 14 MB was observed on this Mac.
How much CPU is normal for PerfPowerServices?
Low CPU, usually well under 1%, with short bursts. Its memory use is moderate for a daemon and stays fairly stable.
How do you stop PerfPowerServices from using so much CPU?
- Let it finish a burst. Short peaks while it writes archives are expected and pass on their own.
- Look for an unusually busy Mac. If PerfPowerServices is busier than usual, the Mac is usually generating more power events than usual: check Activity Monitor's Energy tab for apps with high Energy Impact.
- Restart if it stays high. Sustained high CPU from it is not expected. A restart starts it fresh.
When should you worry about PerfPowerServices?
PerfPowerServices using a large share of CPU for hours is unusual. Note the time and restart; if it repeats, Apple Support can use a sysdiagnose to look into it.
A copy outside /usr/libexec would not be Apple's.
How do you check PerfPowerServices in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type PerfPowerServices 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 PerfPowerServices 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 'PerfPowerServices' | grep -v grep
sudo fs_usage -w -f filesys <PID> # PID from the ps line above
How can Thrum help with PerfPowerServices?
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 PerfPowerServices 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 PerfPowerServices
Can I disable PerfPowerServices?
No. launchd keeps it running and there is no setting for it.
Does PerfPowerServices send data to Apple?
Its man page describes managing local archives of power and performance data. Sending diagnostics to Apple is controlled by your Analytics & Improvements settings.
Sources
- PerfPowerServices(8) man page: run man PerfPowerServices in Terminal
- launchd job: run plutil -p /System/Library/LaunchDaemons/com.apple.PerfPowerServices.plist in Terminal