# Why your Mac is running slow, and which number tells you why

> Before you buy more RAM or run a cleaner app, read the three numbers macOS already shows you: CPU, memory pressure and free space, and what each one means.

Source: https://www.ribbonmac.com/guides/why-is-my-mac-running-slow · Updated 2026-11-19

The version of this page everyone writes is ten tips: empty your caches, restart, close tabs, free up space, buy more RAM. Most of it is guesswork with a nice picture on top, and it gives you no way to tell which of the ten was the one that mattered.

There is a shorter way. A Mac that has become slow is short of one of three things, and macOS already reports on all three. Read them in order and you will know within a few minutes whether the problem is the processor, the memory or the disk, which is the only question worth answering before you start changing things.

One honest note on sources first, because it explains why this page looks the way it does. Apple has an article for a slow iPhone or iPad. It does not have the equivalent for the Mac. The Mac answers are spread across the Activity Monitor guide, which is where the CPU, memory and energy definitions below come from, and the storage article, which is where the disk section comes from. Every figure quoted as a measurement was read on the Mac this was written on: an M1 Pro with 32 GB of memory on macOS 27.0.1, up for 24 days, running a load average around five. It is a busy machine, which makes it a useful one to read.

## Start at the bottom of the Activity Monitor window

[Activity Monitor](https://www.ribbonmac.com/guides/activity-monitor-mac) lives in Applications, inside the Utilities folder. Press Command and the space bar, type the name, and it is two keystrokes away.

Click CPU, then look at the strip along the bottom of the window before you look at anything else. Apple's guide says that clicking CPU shows the number of open processes and threads at the bottom of the window, and that one line answers a question people spend a lot of time worrying about:

```sh
$ top -l 1 -n 0 | head -4
Processes: 2238 total, 5 running, 2233 sleeping, 9661 threads
Load Avg: 5.29, 5.34, 5.25
CPU usage: 20.83% user, 18.16% sys, 60.99% idle
```

Two thousand processes, and 2,233 of them are asleep. That is normal and it costs nothing, because a sleeping process is not using the processor. The number that matters is the five that are running, and the fact that 61 per cent of this Mac was idle at the moment it was read. It did not feel slow, and it should not have.

The three percentages on that line are worth knowing, because Apple defines each one: System is the share of CPU capacity going to processes that belong to macOS, User is the share going to apps you opened, and Idle is the share going unused. If System is the high one, your slowdown is inside macOS. If User is, it is something you launched.

## The first number: what the CPU column says

Click the % CPU heading to sort. Apple's figures refresh on a timer rather than continuously, so watch for a few updates before deciding, and use View > Columns if the column you want is hidden.

Here is the top of the list on this machine, read at the same moment as the line above:

```sh
$ ps -Ao pid,%cpu,%mem,comm -r | head -5
  PID  %CPU %MEM COMM
11276  29.6  0.1 .../Gobble.app/Gobble
  812  26.7  0.3 /Applications/Falcon.app/.../FileAnalysisService
  483  17.9  0.5 /System/Library/PrivateFrameworks/SkyLight.framework/Resources/WindowServer
28737  16.6  0.1 .../SimMetalHost.xpc/Contents/MacOS/SimMetalHost
  707  11.5  1.1 /Library/SystemExtensions/.../com.crowdstrike.falcon.Agent
```

Four processes reading 30, 27, 18 and 17 per cent looks like a machine in trouble. Add them up and it is about 91 per cent, and then you remember that the percentages are measured against a single core. On a ten core Mac that is roughly nine per cent of the computer. [The WindowServer page](https://www.ribbonmac.com/guides/what-is-windowserver-on-mac) has the measurement that makes this concrete: a four thread test program reported itself at 396 per cent on the same ten core machine, because four cores out of ten is 40 per cent of it. A process can read above 100 per cent and still be using a small corner of your Mac.

So the CPU column is not a verdict, it is a pointer. What matters is whether one process is both high and climbing, and whether you recognise it. The names that show up most often are not mysterious:

**A browser renderer.** Every tab in a modern browser can be its own process, and one badly behaved page can hold a core on its own.

**A simulator, a virtual machine or a game.** These ask for the machine on purpose. If you launched one, you already know.

**A security or backup agent.** They scan files, they run on a schedule you did not set, and they are usually the least welcome guest on the list.

**configd, when the network is churning.** The daemon that configures networking does a burst of work every time the Wi-Fi joins, roams or renews a lease, so a high number usually means the network is changing, not that the daemon is broken. [It has its own page](https://www.ribbonmac.com/guides/configd-mac).

**WindowServer, which is the Mac's own drawing.** It redraws whenever anything on screen changes, and [it has its own page](https://www.ribbonmac.com/guides/what-is-windowserver-on-mac) because the number surprises people. If it is high, look at what you have open rather than at WindowServer itself.

**kernel_task, if the Mac is hot.** Apple's explanation is that this process exists partly to slow the CPU down when it gets too hot. It is a heat report rather than a cause, and [there is a page for that too](https://www.ribbonmac.com/guides/what-is-kernel-task-on-mac).

**Spotlight or a photo library rebuilding.** These run for a day or so after a system update and then stop. If a restart is not recent, this is not your answer. It is also the one case on this list you can watch working, and [what Spotlight indexing is doing](https://www.ribbonmac.com/guides/what-is-spotlight-indexing-on-mac) names the processes to look for, `mds_stores` included. Photos has its own version of the same job, [photoanalysisd](https://www.ribbonmac.com/guides/photoanalysisd-mac), which reads a library that just grew by a few thousand pictures.

**launchd, eleven and a half minutes a day, deciding what runs at all.** This is process 1, the first thing the kernel starts and the parent of every daemon in this list, and [the launchd page](https://www.ribbonmac.com/guides/launchd-mac) measured it at about eleven and a half minutes of processor time a day for all of it, the second heaviest quiet process measured in this series, at 25 MB of memory. It has run for every second of the Mac's uptime because the alternative is a kernel panic. When its CPU column climbs for an hour, it is not launchd's own work: half an hour of its log held 7,536 lines of spawn and cleanup paperwork for other processes, and the log names the process id doing the looping. Nothing to quit here. Find the client.

**Finder, six minutes a day, running the desktop and every file window.** This is the file manager as a process, the app that draws the desktop icons, every folder window, the copy dialog and the Trash, and [the Finder page](https://www.ribbonmac.com/guides/finder-mac) measured it at about six minutes of processor time a day with 52 MB of memory and one unbroken run all session, while the Dock next to it restarted once on its own. When its column climbs it is doing visible work, previews, sorts, copies, a slow network volume, and the classic reset is safe: killall Finder closes the windows and relaunches in about a second.

**Dock, a minute and a half a day, drawing the bar at the bottom of the screen.** This is the taskbar as a process, the app that holds your pinned icons, the Downloads stack, the Trash icon, the Spaces thumbnails and the shelf where minimised windows wait, and [the Dock page](https://www.ribbonmac.com/guides/dock-mac) measured it at about a minute and a half of processor time a day with 15 MB of memory and one silent restart three and a half days into a 29 day session. When its column climbs the work is usually visible, magnification sweeps, live stack previews, full screen transitions, and the classic reset is safe: killall Dock blinks the bar out and back in about a second.

**bird, if iCloud Drive is syncing.** It is Apple's iCloud Drive daemon, and uploading is the expensive half of its job, which is why it gets busy the day Desktop and Documents Folders is switched on and then goes quiet. [What the bird process is](https://www.ribbonmac.com/guides/bird-process-mac) covers how much of its memory and CPU use is normal, and what actually helps when syncing stalls.

**syspolicyd, in bursts that line up with app launches.** It is the Gatekeeper check, and it is the process behind the Verifying dialog you see the first time an app opens. It is not a background drain: [the syspolicyd page](https://www.ribbonmac.com/guides/syspolicyd-mac) reads its own log and finds it spent about 2 hours 15 minutes of processor time across 25 days, in short bursts around scans and maintenance jobs rather than a steady trickle.

**cfprefsd, if an app is stuck in a preference loop.** It is the daemon every app's settings reads and writes go through, so a high number is never really about it: some client is hammering preferences, and [the cfprefsd page](https://www.ribbonmac.com/guides/cfprefsd-mac) shows the log line that names the process id of every client that connects, which is how you find the loop.

**sandboxd, briefly, around app launches and permission changes.** It is the paperwork half of the Mac's sandboxing system, and it barely registers: [the sandboxd page](https://www.ribbonmac.com/guides/sandboxd-mac) measured it at under two seconds of processor time a day, because the blocking itself happens in the kernel and only the reports and permission brokering pass through the daemon. If it ever looks busy, some app is generating a stream of denials, and the kernel's log names which one.

**remoted, while developer tools or a connected iPhone are doing something.** The device discovery switchboard costs [the remoted page](https://www.ribbonmac.com/guides/remoted-mac) about four seconds of processor time a day when nothing is plugged in, but a busy hour of device enumeration can push thousands of lines through its log and light up the CPU column for a moment. The daemon's log names the client process id on every request, so if it ever stays busy, the log tells you which tool is driving it.

**symptomsd, in bursts whenever the network changes state.** This is the daemon that takes the Mac's network pulse, scoring Wi-Fi signal quality and every TCP connection against a baseline, and [the symptomsd page](https://www.ribbonmac.com/guides/symptomsd-mac) measured it at about one minute 51 seconds of processor time a day, a tenth of one per cent of one core. It reacts rather than ticks: four asleep hours produced zero log lines while the busiest waking hour produced 4,749, so a glance at the wrong moment can flatter it. If it ever stays busy, the network is flapping somewhere, and its log names the interface and the reason.

**fseventsd, in storms whenever files change.** This is the diary of file changes that Spotlight, backup software and sync tools all read instead of rescanning your drive, and [the fseventsd page](https://www.ribbonmac.com/guides/fseventsd-mac) measured it at about five minutes 15 seconds of processor time a day, a third of one per cent of one core. It tracks your files, not a clock: its busiest hour wrote 45,878 log lines, about 12 a second, during an evening of builds, while a quiet morning hour wrote 277. If it ever stays busy, something is churning files, and it is nearly always a client's errand: a big build, a backup, or a sync tool reconciling.

**airportd, five minutes a day, tending the radio.** This is the Wi-Fi daemon, the process that scans, joins, roams and holds the link statistics for the wireless interface, and [the airportd page](https://www.ribbonmac.com/guides/airportd-mac) measured it at five minutes and one second of processor time a day over 28 days without exiting once. It is the chattiest process in the whole daemon series, eight log lines a second of signal and rate measurements, and the chattiness is free: the busiest event in its own log reports its cost as 48 microseconds. When its CPU column climbs for an hour, the culprit is upstream, a flapping signal, a hidden network being scanned for, or a roam loop between two routers, and the fix is network side, not in the daemon.

**spindump, briefly, right after something hangs or blows a budget.** This is the daemon that writes the reports macOS keeps about misbehaving software, the .diag files piling up in /Library/Logs/DiagnosticReports, and [the spindump page](https://www.ribbonmac.com/guides/spindump-mac) measured it at roughly one run a day. It samples every process on the machine for ten seconds when you force quit a stuck app, which is why it can itself flash to the top of Activity Monitor for a moment, then it exits and goes quiet. A spindump that is busy is not the problem, it is the notary: something else hung, or a process crossed a stated CPU or disk write limit, and the report it left behind names which.

**usernoted, in small bursts whenever a banner or badge appears.** This is the daemon that delivers every notification on the Mac, the banners, the Dock badges, the list Notification Center keeps, and [the usernoted page](https://www.ribbonmac.com/guides/usernoted-mac) measured it at about 36 seconds of processor time a day. It runs as your own user rather than root, it never exits, and when it does show up in the CPU column it is carrying someone else's message: a chat app catching up, a calendar looping on invites, an app re posting a failed alert. The sender's row in System Settings under Notifications is the fix, not the daemon.

**installd, in shifts while software is being installed.** This is the daemon that puts packages and App Store updates where they belong, and it works like a tradesman with a pager: no keep alive, summoned when something installs, released when memory is wanted. [The installd page](https://www.ribbonmac.com/guides/installd-mac) measured its current shift at about two and a half seconds of processor time in a day and a half, on both of its twin processes combined. When it does burn CPU it is real work, decompressing and verifying and moving an update into place, and the processor budget report it earns on those days names the install. If it stays busy with nothing installing, an installer is stuck, and the install log names the package.

**softwareupdated, ten seconds a day, deciding when everything else updates.** This is the daemon behind Software Update, the one that checks Apple's catalog every six hours, remembers every update this Mac was offered, counts the nights you pressed later, and stages downloaded updates in /Library/Updates until their night comes, and [the softwareupdated page](https://www.ribbonmac.com/guides/softwareupdated-mac) measured it at about ten seconds of processor time a day with half a gigabyte of staged update under its watch. It never installs anything itself; it hands the finished job to installd. When it shows CPU or network for a stretch, something is being downloaded or verified, and the Software Update pane will name it.

**chronod, ten seconds a day, keeping your widgets on time.** This is the timeline daemon, the process that decides when each desktop and Notification Centre widget refreshes, launches the extensions that draw them and forwards live activities to nearby accessories, and [the chronod page](https://www.ribbonmac.com/guides/chronod-mac) measured it at one run in 29 days and about ten seconds of processor time a day on 45 MB, with an hour of its log showing 1,790 lines of quiet scheduling. Its launch file is an appointment book: after every refresh it books its own next wake up, an event 1,549 seconds out. When it does run busy, the log names the widget responsible, and every booted iOS simulator adds another chronod copy, so the fix is usually a widget or a simulator, not the daemon.

**backupd, eleven seconds a day, waiting for a backup disk that was never plugged in.** This is the Time Machine engine, the root process that would copy your whole Mac onto an external disk every hour if one were configured, and [the Time Machine page](https://www.ribbonmac.com/guides/time-machine-mac) measured it at one unbroken run of 30 days, about eleven seconds of processor time a day on 3.5 MB of memory, on a Mac with zero destinations, zero local snapshots and a status line reading Running = 0. The app with the clock icon turns out to be a 336 KB doorbell that rings this process; the engine itself lives in CoreServices and has been awake the whole month for a job this Mac never gave it. When its CPU column does climb on a configured Mac, a backup is genuinely running and the first one to a new disk can take hours. The fix for a stuck one is never the daemon, it is the disk, the cable or the exclusion list.

**sysmond, a minute and a quarter a day, answering Activity Monitor.** This is the system monitor daemon, the root process that gathers the per-process statistics Activity Monitor displays, and [the sysmond page](https://www.ribbonmac.com/guides/sysmond-mac) measured it at about a minute and a quarter of processor time a day on a Mac that polls process statistics all day, with quiet stretches at 0.05 seconds in three and a half minutes and zero log lines in six hours. Its launch file has no schedule at all: it wakes when a client connects to its one Mach door, and the system reclaims its memory when the questions stop, four deliberate idle exits in 29 days. When its CPU column climbs, a client is asking, usually the app itself left at a 1 second update frequency or one menu bar stats tool too many.

**secd, half a minute a day, holding every password on the Mac.** This is the keychain daemon, the process that runs every keychain lookup for every app, and [the secd page](https://www.ribbonmac.com/guides/secd-mac) measured it at about 34 seconds a day with an uptime matching your login. Where sysmond stayed silent for hours, secd logged 2,830 lines in 45 minutes, each one a SQL query against the keychain database, and 86 percent of them came from one office suite fetching the same 25 items three times in a single second. When its CPU column climbs, an app is looping on keychain lookups: sign that app out and back in. Quitting the daemon itself changes nothing, launchd restarts it on the next knock.

**appstoreagent, five seconds a day, minding the store.** This is the App Store's background agent, the process that checks for app updates, validates the receipts inside store-bought apps and handles in-app purchases whether or not the App Store app is open, and [the appstoreagent page](https://www.ribbonmac.com/guides/appstoreagent-mac) measured it at about five seconds of processor time a day, among the cheapest in this list, with a log that shows one push connection check every ten minutes and nothing else. When its CPU or network column moves, store business is underway, usually an update download, and the automatic updates switches in the App Store pane of System Settings are the levers. It never installs anything; the parcels go to installd, and a maintenance sweep it shares with the scheduler dasd a few minutes after login is schedule, not fault.

**assistantd, in short bursts while you talk to your Mac.** This is the Siri and dictation daemon, the process behind every Hey Siri and every dictated sentence, and [the assistantd page](https://www.ribbonmac.com/guides/assistantd-mac) measured it at about five seconds of processor time a day, level with the store agent, among the cheapest in this list. It is worth recognising for two things: it keeps its checkpoint state in the login keychain, so it is one of the daemons that can show up in the keychain access prompt, and if you ever see three of them in Activity Monitor at once, two belong to booted iPhone simulators rather than to anything sinister.

**CommCenter, two seconds a day, waiting for a call.** This is the phone call daemon, the iPhone-inherited process that relays calls and texts through your iPhone, and [the CommCenter page](https://www.ribbonmac.com/guides/commcenter-mac) measured it at about two seconds of processor time a day, in the cheapest band of this list, with a scoreboard of SMS and cellular counters that has read zero since the day the Mac was set up. It earns its place here for the one thing people actually notice about it: it keeps its call credentials in the login keychain, so after a password change it is the name most likely to appear in the CommCenter wants to use the login keychain prompt, and allowing it once with the old password ends the asking.

**replayd, three seconds a day, ready to record.** This is the daemon behind ReplayKit, the framework apps use to record or broadcast themselves, and [the replayd page](https://www.ribbonmac.com/guides/replayd-mac) measured it at about three seconds of processor time a day, level with the phone call daemon, with a log that stayed silent for half an hour until a single screenshot woke it: it is also the machinery that grabs the frame for the system's own screenshots. When its CPU column moves, a recording, a broadcast or a screenshot is genuinely running, and the app doing it is the thing to close, not the daemon.

**accountsd, seven seconds a day, minding every account.** This is the accounts daemon, the process that stores and hands out the sign-ins for iCloud, Google, Exchange and every other internet account on the Mac, and [the accountsd page](https://www.ribbonmac.com/guides/accountsd-mac) measured it at about seven seconds of processor time a day, in the cheap band of this list, with a log that is a census of its clients: the iCloud, identity and contacts daemons all line up at its counter, the App Store's account agent 58 times a day. It earns its place here for the prompt people meet after a password change, accountsd wants to use the login keychain, whose two-click answer, Always Allow with the current password, retires it for good.

**usbmuxd, under a second a day, waiting for a phone.** This is the iPhone cable daemon, the switchboard every conversation between a plugged-in iPhone and the Mac runs through, over one world-writable socket at /var/run/usbmuxd, and [the usbmuxd page](https://www.ribbonmac.com/guides/usbmuxd-mac) measured it at 21 seconds of processor time across 28 days, at the cheap end of this list, with a log that read zero lines for a week straight because no phone came near the machine. It cannot burn CPU thinking about phones, only talking to them, so when its column does climb the cause is physical: a cable, hub or port that keeps dropping the connection, and the hardware, not the daemon, is what to change.

**systemuiserver, half a second a day, owning the right end of the menu bar.** This is the process that draws the status area of the menu bar and sits in the path of every screenshot shortcut, and [the SystemUIServer page](https://www.ribbonmac.com/guides/systemuiserver-mac) measured it at 17 seconds of processor time across 29 and a half days, the cheapest process in this entire list, with zero log lines in a 20 minute window and 3.6 MB of memory. When its column does climb, real interface work is underway: menus, status items, a capture. The two decade old remedy still works and is still the whole fix: killall SystemUIServer, and the menu bar flashes and returns.

**loginwindow, two minutes a day, running the session's front desk.** This is the process that draws the sign in screen and the lock screen, raises the out of memory dialog and the crash warning after a bad restart, and then spends your whole session as the registrar, writing down every app that opens or closes, and [the loginwindow page](https://www.ribbonmac.com/guides/loginwindow-mac) measured it at 63 minutes of processor time across 29 and a half days with 30 MB of memory and one unbroken run. It is the one process in this series where killall is never the fix, because killing it does not refresh anything, it logs you out. When its column does climb, volume is the cause: an app crash loop feeding the registrar, or a second session alive from fast user switching or screen sharing.

**familycircled, a second and a half a day, keeping the family group straight.** This is the Family Sharing roster daemon, the process that knows who is in your circle, which members are children, and whether an app may be told your age range, and [the familycircled page](https://www.ribbonmac.com/guides/familycircled-mac) measured it at 6.4 seconds of processor time across four days on under 10 MB of memory, woken four ways: a daily cache refresh that waits for the charger, a heartbeat, a rule change when someone moves country, and a notification whenever your contacts change. If you are in no family group at all it still runs, with almost nothing to do.

**calaccessd, well under a second of CPU a day, keeping your calendars in step.** This is the calendar data daemon, the front door every app that reads or writes events knocks on, and [the calaccessd page](https://www.ribbonmac.com/guides/calaccessd-mac) measured it at 0.43 seconds of processor time in the 18 minutes after launch, all of it start-up cache work, with none added in the checks that followed, relaunched 19 times in 29 days. Its column only climbs when a sync is genuinely stuck, and its real cost is not CPU but patience: the kernel's own sleep log once showed it holding the walk into sleep for up to 30 seconds while it finished saving, so a Mac that takes a long breath before sleeping may simply have a calendar settling.

**dataaccessd, about a second of CPU a day, logging into your calendar servers.** This is the calendar sync daemon, the sibling that owns the accounts while calaccessd owns the database, and [the dataaccessd page](https://www.ribbonmac.com/guides/dataaccessd-mac) measured it at 0.95 seconds in the first hour of a run, all of it around launch and one midday refresh, with zero added in later checks, relaunched roughly every day and a half. It loads one plugin per protocol, CalDAV, CardDAV, Exchange, LDAP, from the Address Book Plug-Ins folder, and it is the process behind the Enter the password for the account dialog, because it is the one that tried the login. A busy dataaccessd means a busy account: a stuck password prompt or a server that keeps timing out.

**knowledgeconstructiond, five runs in 29 days, and only on the charger.** This is the Apple Intelligence knowledge graph daemon, the process that reads your messages, photos and contacts and weaves them into the on-device map that powers suggested names for group chats, and [the knowledgeconstructiond page](https://www.ribbonmac.com/guides/knowledgeconstructiond-mac) measured it as barely a process at all between runs: zero log lines in a three hour window, five launches in 29 days, because its main job carries RequiresExternalPower and the rest refuse the battery outright. It earns its column only during the catch-up sitting after you plug in, and when that sitting runs long the system steps in and recycles it at its own memory cap, which is why the row you notice is memory, not CPU. If it never ran, nothing would break, but your group chats would stop naming themselves.

**audiomxd, nine seconds a day, deciding where your sound goes.** This is the audio route arbitration daemon, the referee that decides which nearby Apple device your AirPods belong to when two of them want the same headphones, and [the audiomxd page](https://www.ribbonmac.com/guides/audiomxd-mac) measured it at about nine seconds of processor time a day on 6 MB of memory, one continuous run since boot, with a launch file whose routing doors are mostly still locked behind feature flags. It grew up on the iPhone, where its name is a battery thread regular, and the Mac got the same daemon almost free. When its CPU column climbs, a negotiation is looping somewhere, usually a headset flipping between two devices, and the referee is the wrong one to blame.

**captiveagent, a tenth of a second per run, asking the Wi-Fi one question.** This is the captive portal daemon, the process that fetches Apple's 69 byte test page every time you join hotel or airport Wi-Fi and raises the login sheet when the network answers with a form instead, and [the captiveagent page](https://www.ribbonmac.com/guides/captiveagent-mac) measured it at 19 runs in 29 days, started on demand by a Mach message and gone again at the next idle exit. Its sandbox allows outbound connections only, so it cannot accept anything from the network it is probing, and no high CPU row exists anywhere in its search family. If a portal ever loops it, the fix is the voucher at the desk, not the process.

**universalaccessd, four seconds a day, keeping Accessibility alive.** This is the Accessibility server, the process that holds the settings for Zoom, Sticky Keys, Mouse Keys and Live Speech from login to shutdown, and [the universalaccessd page](https://www.ribbonmac.com/guides/universalaccessd-mac) measured it at one run in 29 days and about four seconds of processor time a day, in the cheapest band of this list. It runs as your own account rather than root, never gets reclaimed under memory pressure, and the only movement in its log is audio: the connection that lets accessibility features beep and speak. When something in its family does run heavy, it is the on demand visual agent that draws zoom and hover text, not the clerk.

**mdworker_shared, a tenth of a second each, in shifts that never end.** This is the Spotlight import worker, the process that opens files and reads them for the search index, and [the mdworker page](https://www.ribbonmac.com/guides/mdworker-mac) measured 82 of them passing through a single hour, spawning in pairs and dying when the job ends, six alive at one sample with no more than 0.13 seconds of CPU each. The worker is a unit of work, not a resident program, so its column only matters in aggregate: a long column of them climbing together means a backlog, an update that unpacked thousands of files, a migration, a restore, a sync client that just landed a project. Apple's own article on Spotlight indexing says the honest thing about that state: depending on the amount of data on your device, indexing can take hours or even days.

**apsd, never, because quitting is not its job.** This is the Apple Push Notification daemon, the process that holds one permanent connection open to Apple's servers on port 5223 so messages and alerts can arrive on a machine that is doing nothing, and [the apsd page](https://www.ribbonmac.com/guides/apsd-mac) measured it at about 38 seconds of processor time a day over 27 days without ever exiting. It runs as root, it is one of the few daemons the system has promised not to reclaim under memory pressure, and its CPU column stays at zero almost always. The work people mistake for it belongs to its clients, 51 processes on the measured Mac, from iMessage to the App Store to shared photo albums, so a busy apsd means a busy delivery round, not a daemon gone wrong.

**tccd, two and a half minutes a day, remembering what you allowed.** This is the privacy permissions daemon, the process behind every allow-access-to-your-camera question on a Mac, and [the tccd page](https://www.ribbonmac.com/guides/tccd-mac) measured the copy running as the user at about two and a half minutes of processor time a day, with a root twin under it adding about a minute more, while its log produced zero lines in two hours of watching, because a permissions daemon only speaks when something changes. When its CPU column climbs, the volume is real: a prompt on screen, an app re-asking after an update, or a management profile flipping overrides. The levers are the rows in the Privacy and Security pane of System Settings, which is a viewer onto this daemon's own database.

**logd, in nine-minute days, writing everything down.** This is the unified logging daemon, the clerk that every other process hands its log lines to, and [the logd page](https://www.ribbonmac.com/guides/logd-mac) measured it at just under nine minutes of processor time a day, the heaviest of the quiet background daemons in this list. It earns the title honestly: it is the funnel for the whole system, so when [logd](https://www.ribbonmac.com/guides/logd-mac) shows up in the CPU column, the work belongs to whichever process is shouting the loudest, and the daemon's own statistics file names the talkers to the byte. The system considers it so load bearing that repeated crashes are answered with a deliberate kernel panic, so there is nothing to quit and nothing to fix here, only a loud neighbour to find.

**contactsd, thirty one seconds a day, minding everyone you know.** This is the Contacts daemon, the process under the Contacts app that manages the contacts database and serves every app that looks a person up, and [the contactsd page](https://www.ribbonmac.com/guides/contactsd-mac) measured it at about thirty one seconds of processor time a day and 3.3 MB of memory, among the smallest in this list. Unlike most here it runs as your user, not root, and the system is happy to reclaim it and start a new one, twenty runs so far on the measured Mac. When its CPU column does move, the daemon is the messenger: the account still syncing in Contacts settings is the problem, not the clerk.

**replicatord, nineteen seconds a day, when an iPhone is in the room.** This is the remote widget sync daemon, the process that keeps iPhone widgets on the desktop fresh and carries the device data behind iPhone Mirroring, and [the replicatord page](https://www.ribbonmac.com/guides/replicatord-mac) measured it at about nineteen seconds of processor time a day on 5 MB of memory, woken 26 times in a day and a half by the radio hearing a phone nearby, with a log that names the other end by model. It only works when there is something to talk to, and the off switch is a real one: System Settings, Desktop and Dock, Widgets, Use iPhone widgets. If it ever stays busy with no phone around, its log names the device doing the talking, and the simulators developers leave booted each run a copy of it.

**netbiosd, a quarter second a shift, answering to a name from 1987.** This is the NetBIOS daemon, the registrar that announces your Mac on the old workgroup naming protocol and defends its name if another machine claims the same one, and [the netbiosd page](https://www.ribbonmac.com/guides/netbiosd-mac) measured it at 2.8 MB of memory and a quarter of one second of processor time over an eight hour life, the smallest footprint in this list. It runs as its own reserved account, restarts about twice a day with the network, and the firewall prompt it can trigger is just its two UDP listening ports doing their job. If it ever runs hot, look for two machines with the same name, not for a broken daemon.

**routined, sixteen seconds a day, learning where you go.** This is the location learning daemon, the quiet half of the location pair that turns the position fixes [locationd](https://www.ribbonmac.com/guides/locationd-mac) collects into places, patterns and predicted next stops, and [the routined page](https://www.ribbonmac.com/guides/routined-mac) measured it at about sixteen seconds of processor time a day and 32 MB of memory, the price of the three Core ML models and the learned-visit database schema it carries. It runs as your own user, it has not exited once in 27 days on the measured Mac, and the crash reports filed under its name all came from iPhone simulators missing a shutdown deadline, not from the daemon failing. The off switch is Significant Locations under Location Services in Privacy and Security.

**suggestd, twenty-one seconds a day, reading your mail so Search can guess.** This is the Siri Suggestions daemon, the guessing engine behind the app Spotlight offers before you finish typing and the word QuickType slides in. [The suggestd page](https://www.ribbonmac.com/guides/suggestd-mac) measured its sixteen scheduled background jobs, most of which refuse to run on battery, a live power budget of 500 operations, and a cost of about twenty-one seconds a day and 42 MB. It keeps what it learns in two directories in your own Library that even your own account cannot read into, and it filed no crash reports at all on the measured Mac. The off switches are the Suggestions settings in the Siri pane, per app.

**identityservicesd, sixteen seconds a day, vouching that this Mac is really yours.** This is the Apple Account and iMessage identity daemon, the process that registers your phone number for iMessage, keeps the keys and device list, and shows the warning when a new device joins your account, and [the identityservicesd page](https://www.ribbonmac.com/guides/identityservicesd-mac) measured it at about sixteen seconds of processor time a day and 20 MB of memory behind the biggest binary in this series, 30 MB of signed Apple code with no manual page. It runs as your own user, it has not exited once since boot on the measured Mac, and it files the new-device notification in its own words. Its data sits behind the same privacy wall as the others: ask for it directly and the answer is Operation not permitted.

**opendirectoryd, nineteen minutes a day, the heaviest quiet one in this list.** This is the account database daemon, the process the login screen asks who you are, and [the opendirectoryd page](https://www.ribbonmac.com/guides/opendirectoryd-mac) measured it at about nineteen minutes of processor time a day and 1.3 percent of one core, double logd, while answering roughly a hundred and eighty thousand identity and group questions a day, nearly all from cache in about a microsecond. It runs as root, it has never exited once on the measured Mac, and its own launch configuration carries a clause that would rather stop the whole machine than keep running after back to back crashes. When its CPU column climbs for hours, the daemon is the messenger: something is asking who owns what, usually a backup tool or a build, and odutil show nodes names the client.

Then click Energy, which is the tab people forget. Apple describes Energy Impact as a relative measure of the current energy consumption of the app, where lower is better, and 12hr Power as the average energy impact of the app over the last 12 hours. That second column only appears on a laptop, and it is the one that catches a process that works in short bursts and looks innocent on a single CPU reading. The same tab also shows whether App Nap is active for an app, and whether anything is preventing your Mac from going to sleep. If it is the battery rather than the CPU that brought you here, [the battery drain page](https://www.ribbonmac.com/guides/why-is-my-mac-battery-draining-so-fast) takes that tab apart, reads the health numbers underneath it, and names the commands that list whatever is holding sleep off.

## The second number: memory pressure

Click Memory. Apple's own list of what you will see there is short: Memory Pressure, Physical Memory, Memory Used (broken into App Memory, Wired Memory, Compressed and Cached Files), and Swap Used.

The graph at the bottom is the part to read first, because Apple gives it three colours and a meaning for each one:

**Green means your computer is using all its RAM efficiently.** Not short of memory. Nothing to buy.

**Yellow means it might eventually need more RAM.** Worth watching rather than acting on.

**Red means it needs more RAM.** That is as blunt as Apple gets.

The sentence that follows is the one that saves people money, and it is the opposite of what most advice says: when you have free or unused memory, your computer performance does not necessarily improve, because macOS gets its best performance by efficiently using and managing all of your memory. Empty memory is wasted memory. That is why a Mac sitting at 90 per cent memory used can be perfectly fast, and why an app that "frees up RAM" is usually taking away a cache that was helping you.

The confusing part, and the reason the numbers on this machine are worth printing, is that two tools will give you two different answers about how much memory is free:

```sh
$ top -l 1 -n 0 | grep PhysMem
PhysMem: 31G used (6448M wired, 7715M compressor), 181M unused.
$ memory_pressure | tail -1
System-wide memory free percentage: 55%
```

Both are true, and the gap is the whole point. The first line counts only pages that are genuinely unused, which on a Mac that has been up for three weeks is almost none: everything else is either in use or holding a file that was read recently. The second counts the memory the system can hand over immediately if something asks, including the file caches.

You can see it page by page if you want to check the arithmetic:

```sh
$ vm_stat | head -5
Mach Virtual Memory Statistics: (page size of 16384 bytes)
Pages free:                                     6402.
Pages active:                                 565547.
Pages purgeable:                                6212.
```

That page size, 16,384 bytes, is what makes the numbers small and the story clear. Free pages at 6,402 and purgeable pages at 6,212 come to about 200 MB together, which is the same order as the 181 MB the first tool called unused. Neither figure is wrong. They are counting different things, and once you know that, the "why does it say 55 per cent free when my Mac says it has no memory left" question answers itself.

The one number here that does deserve attention is swap, the space on your startup disk macOS is using to hold memory it has moved out of the way:

```sh
$ sysctl vm.swapusage
vm.swapusage: total = 7168.00M  used = 5845.88M  free = 1322.12M  (encrypted)
```

Five and a half gigabytes of swap in use. On a modern Mac with a fast SSD this is not the disaster it was on a laptop with a spinning disk, and some swap is normal on a machine that has been running for weeks. But a swap figure that grows while you work, alongside a memory pressure graph that sits yellow or dips red, is the honest sign that the machine wants more memory than it has. The compressor column tells the same story from the other side: 7,715 MB of memory compressed to make room, which is real work your processor is doing so that something else can run.

## The third number: free space on the startup disk

Open System Settings, click General, then Storage. Apple's article on freeing up space walks through the categories that appear, and mentions that where you see a More Info button beside a category you can click it to find out what is in there and manage it.

On this Mac the disk reads 926 GB with 610 GB used and 285 GB available, which is comfortable. But the percentage is the figure to notice: a drive at 69 per cent used has room to breathe, and the same 285 GB free on a much smaller drive would not.

The category that sends people looking is [System Data](https://www.ribbonmac.com/guides/what-is-system-data-on-mac), and Apple's definition of it is refreshingly plain: it is a general category that measures the storage space used by all Apple and third party files that do not belong to any more specific category. In other words it is the leftovers, not a hidden folder of junk, and there is nothing in it to delete directly. It grows with caches, local snapshots, application support files and the sleep image, which is a copy of memory written to disk so the machine can resume quickly:

```sh
$ ls -lh /private/var/vm/sleepimage | awk '{print $5, $9}'
2.0G /private/var/vm/sleepimage
```

Two gigabytes, on a 32 GB Mac, and it is doing a job. Worth knowing about rather than worth deleting.

Two things Apple says that people routinely miss. First, when you move a file to the Bin its storage space does not become available until you empty the Bin, so the "I deleted 40 GB and it changed nothing" report is usually this. The full set of reasons is longer than most people expect, and [the storage page that starts from exactly that confusion](https://www.ribbonmac.com/guides/mac-storage-full-but-nothing-on-it) works through them, including the system volumes and the hidden folder that account for the rest. Second, the Storage pane has its own recommendations, and the three Apple describes are storing files in iCloud, optimising storage by removing films and shows you have already watched and keeping only recent email attachments, and automatically emptying the Bin after 30 days. All three are free and none of them involve a download.

## Can this Mac even take more RAM?

Apple's guide on this is short and worth doing before you open a shop, because the answer changes what you do next. Press and hold the Option key, choose System Information from the Apple menu, click Memory under Hardware on the left, and look for Upgradeable Memory in the Memory Slots pane. Apple's own caveat is in brackets: if the Memory Slots pane does not appear, upgradeable memory is not available for your Mac.

On this machine it does not appear, and the reason is one line of hardware:

```sh
$ system_profiler SPMemoryDataType
Memory:
      Memory: 32 GB
      Type: LPDDR5
      Manufacturer: Hynix
```

No slots, because the memory is part of the chip package on an Apple silicon Mac. So when someone on an M series Mac asks whether more RAM would fix the slowness, the useful answer is not yes or no, it is that the question has changed: there is nothing to add, so the work moves to finding what is using the memory you have.

## Things that look like fixes and are not

**A memory cleaner.** It empties the cache that Apple describes as a performance feature, on the theory that free memory is fast memory. Apple says the opposite in the same document: free or unused memory does not necessarily improve performance.

**Resetting the SMC or the PRAM.** Apple's own SMC article opens with "You most likely do not need to reset the SMC", and for Apple silicon it gives a restart and then says no other steps are needed, because the SMC resets automatically. There is no procedure left to follow on an M series Mac.

**Clearing caches and "cleaning the system".** Safe mode does clear some system caches, and Apple says a side effect can be temporarily more storage space. That is a diagnostic tool, not a monthly habit, and it belongs in the next section rather than this one.

**Buying more RAM before reading the graph.** On a Mac that can take it, this is the most expensive possible way to guess.

**Reinstalling macOS.** Apple does recommend it, but only after the safe mode test has said the problem is software that loads at startup. Doing it first throws away the evidence.

**Force quitting the system processes you do not recognise.** A Mac's process list is mostly Apple's own, and the busiest looking name is often the one doing the most ordinary job. [mDNSResponder](https://www.ribbonmac.com/guides/mdnsresponder-mac) answers every name lookup the machine makes, for every app on it, and quitting it stops name resolution for as long as launchd takes to bring it back.

## If every number looks fine and the Mac still feels slow

Two possibilities are left, and both are testable. There is one thing to rule out before either, though, because it looks like slowness from the outside: a Mac that stays warm and whose fan stays loud is not just busy, it is being managed. Apple documents what happens at the top of its thermal scale, which is fans at maximum speed while the system reduces performance to shed the heat, and [the fan page](https://www.ribbonmac.com/guides/why-is-my-mac-fan-so-loud) covers the whole sequence from the sensor to the sound.

**One app is stuck rather than busy.** If you are staring at a spinning pointer, go back to Activity Monitor, select the process, and click the More button. Apple's list there includes Sample Process, described as a report on a selected process over three seconds, Spindump, which is for unresponsive apps, and System Diagnostics. A sample takes a few seconds and tells you whether the process is working or waiting.

**Something that loads at startup is the problem.** Apple's safe mode article is the way to find out, and the list of what safe mode does is exactly a list of what can slow a Mac down: it prevents software that is not required by macOS from loading at startup, including login items, extensions and fonts that Apple did not install; it performs a basic check of the startup disk; and it clears some system caches. The test is the useful part. If the slowness disappears in safe mode and does not come back after a normal restart, it was one of the things safe mode skipped. If it comes back, Apple says to remove login items in System Settings and restart, or to make a second user account and try there, because that account has none of your startup software. The list you would be working through is in System Settings under General, then Login Items & Extensions, and [the background items page explains what each row and each state means](https://www.ribbonmac.com/guides/background-items-added-mac).

To confirm you are actually in safe mode, press and hold Option while choosing System Information from the Apple menu, click Software, and look for Boot Mode: Safe.

If the problem survives all of that, it may not be software. Apple Diagnostics is Apple's hardware test, and on an Apple silicon Mac you hold the power button until the startup options appear, then press and hold Command and D until the Mac restarts. On macOS Tahoe and later it asks which diagnostic to run, display, keyboard or trackpad, and if it prints a reference code, that code is what you take to a service desk rather than a description of a slow Mac.

And one easy explanation worth checking before any of this: a day or two after a system update, macOS is rebuilding indexes, re-downloading libraries and re-optimising photos. That work is real, it is temporary, and the machine will be itself again tomorrow.

If the slowness has turned into something worse, though, the disk deserves a look, because it is the one explanation on this page that does not fix itself. Apple introduces Disk Utility with the symptoms rather than the cause: multiple apps quit unexpectedly, a file is corrupted, an external device doesn't work properly, or your computer won't start up. Slowness is not on that list, but crashes are, and [First Aid is the check that covers it](https://www.ribbonmac.com/guides/disk-utility-first-aid-on-mac).

## Where window managers fit

A window manager does not make a slow Mac fast, and it is fair to ask whether it adds to the pile. The measurement on the [WindowServer page](https://www.ribbonmac.com/guides/what-is-windowserver-on-mac) is the useful one: moving a window 54 times in ten seconds cost roughly a fifteenth of a second of processor time, against a ten second baseline that had already used two and a third. Arranging windows is not what makes a Mac slow. A runaway process, a full disk or a memory shortage is.

What a window manager changes is how much arranging you do by hand. macOS has [tiling built in](https://www.ribbonmac.com/guides/how-to-tile-windows-on-mac) for halves and quarters, and above that most tools place windows one at a time. Ribbon keeps the windows you are using as a scrolling strip instead, so opening another window makes the strip one column longer rather than making every other window narrower. It is $15, once, for up to 3 Macs, with a full refund within 10 days, and it runs on macOS 14 Sonoma and later on Apple silicon and Intel Macs.

## The short version

Three numbers, in this order. What the CPU column says, and whether one process is high and climbing rather than four processes adding up to a fraction of one core. What the memory pressure graph says, because Apple's green, yellow and red mean exactly what they sound like, and because free memory is not the same thing as fast memory. And how much of the startup disk is free, checking the percentage rather than the gigabytes. If all three read well, the remaining candidates are an app that is stuck, something loading at startup, or a hardware fault, and safe mode and Apple Diagnostics are how you tell those apart. Skip the memory cleaners and the SMC resets, because Apple's own documentation says there is nothing there to fix.

## FAQ

### Why is my Mac suddenly slow?

Sudden is usually specific. A Mac that was fine yesterday and is not today has something new running, and the day after a system update the new thing is often macOS itself, rebuilding an index or re-downloading a library while you work. Open Activity Monitor, click CPU, and sort by % CPU to see what is at the top right now. If the answer is an app you installed or updated recently, you have found it rather than guessed it. If every process looks quiet and the memory pressure graph is green, the slowdown is probably not happening inside the Mac at all: check whether the app that feels slow is waiting on a network request or a file on an external drive.

### Does my Mac need more RAM?

Apple answers this directly with the Memory Pressure graph in Activity Monitor, and it is a traffic light rather than a feeling. Green means your Mac is using all its RAM efficiently, yellow means it might eventually need more RAM, and red means it needs more RAM. Read the colour before you read the gigabytes, because a Mac that is using nearly all of its memory is behaving exactly as designed. If the graph is yellow and often, look at the Memory Slots pane first: press and hold the Option key, choose System Information from the Apple menu, click Memory under Hardware, and see whether an Upgradeable Memory row appears. On an Apple silicon Mac it will not, because the memory is part of the chip package.

### Will a memory cleaner or clearing caches speed up my Mac?

No, and Apple explains why in its own Activity Monitor guide: when you have free or unused memory, your computer performance does not necessarily improve, because macOS gets its best performance by using and managing all of your memory. A chunk of that memory is the file cache, which exists to save you a read from disk, and an app that empties it is taking away help rather than adding any. Clearing caches has one legitimate place, and it is inside safe mode, where Apple says clearing some system caches can temporarily make more storage space available. That is a diagnostic step to see whether the problem is software that loads at startup, not a monthly tune up.

### Why is my Mac slow when I have plenty of storage?

Because storage is only one of the three things that can be short. A Mac with hundreds of gigabytes free can still have every core busy or be short of memory, and neither of those shows up in the Storage pane. In Activity Monitor the memory pressure graph is the fast answer: green means memory is not your problem, yellow or red means it might be. The other half of the storage question is the percentage, not the number. A 512 GB drive with 60 GB free is comfortable, a 2 TB drive with 60 GB free is not, and macOS has fewer places to put a large temporary file on the second one.

### How do I find out which app is slowing down my Mac?

Activity Monitor, sorted correctly. Click CPU, click the % CPU column heading to sort, and watch it for a few updates rather than taking one reading, because Apple's figures refresh on a timer. Remember that the percentages are measured against a single core, so a process reading 150 per cent is using one and a half cores, not 150 per cent of the machine. If nothing stands out on CPU but the Mac is warm and the battery is draining, click Energy instead: Energy Impact is Apple's relative measure of current energy consumption, and 12hr Power averages it across the last 12 hours, which finds a process that works in bursts. For a single app that is stuck, select it in the list and choose Sample Process from the More button, which Apple describes as a report on a selected process over three seconds.
