Mac Memory Pressure: Reading the Yellow Graph in Activity Monitor

The Memory pane is open, the graph at the bottom has gone yellow, and the figure next to Memory Used says almost everything is in use. The obvious conclusion is that the machine is out of memory and something has to be closed. Sometimes that is right. Often the graph is yellow because macOS is doing exactly what it is designed to do, and closing applications will change the number without changing how the machine feels. The difference between those two cases is readable, and it takes about five minutes of watching rather than one glance.

What the graph is actually measuring

Memory pressure is not a percentage of memory used. It is a composite reading, and Apple lists its inputs.

Memory Pressure: Graphically represents how efficiently your memory is serving your processing needs. Memory pressure is determined by the amount of free memory, swap rate, wired memory, and file cached memory. Source: support.apple.com

Two of those four inputs are rates and states rather than totals. Swap rate is how often pages are being moved between RAM and the startup disk, not how much has ever been moved. Wired memory is the portion the system cannot move at all. File cached memory is the part that looks used but is available on demand.

That construction is why the graph disagrees with intuition. A machine holding thirty gigabytes of cached files has very little free memory and a swap rate of zero, and the pressure reading will be green because nothing is being starved. A machine with the same amount reported as used but pages moving to disk constantly will read yellow or red. The totals in both cases look identical. The experience does not.

Memory Used is a description of allocation. Memory pressure is a description of whether that allocation is costing anything. Only the second one is a reason to act.

Yellow is a forecast, not a fault

Apple's definitions of the three colours are short and worth reading exactly rather than in paraphrase.

Green memory pressure: Your computer is using all of its RAM efficiently. Yellow memory pressure: Your computer might eventually need more RAM. Red memory pressure: Your computer needs more RAM. Source: support.apple.com

The phrase in the yellow definition is might eventually. Yellow is not a warning that something is currently broken. It says the working set is close enough to the available memory that the system is having to work to fit it, using compression and swap to make room. Performance may be entirely acceptable in that state, and on a machine that spends most of its day in green with yellow during the busiest hour, nothing needs to change.

Red is different in kind rather than in degree. Red with the machine feeling slow is the one reading in this whole pane that justifies buying hardware, and it is also the reading most often misreported, because a brief red spike while a large application launches is normal and passes in seconds.

The same page also warns against the instinct that produces most bad advice on this subject.

When you have free or unused memory, your computer performance does not necessarily improve. macOS obtains the best performance by efficiently using and managing all of your computer's memory. Source: support.apple.com

Free memory is not an asset being saved for later. It is capacity not being used.

The shape over time decides, not the colour right now

The graph is a time series and it is being read as a single value. That is the most common mistake in this pane, and correcting it turns an ambiguous reading into a clear one.

Three shapes come up repeatedly. A sawtooth, where pressure climbs into yellow and falls back to green each time an application is closed or a task finishes, describes a machine operating at the edge of its capacity but recovering. It is uncomfortable rather than broken. A plateau, where pressure enters yellow in the morning and stays there until the machine is restarted, describes a working set that genuinely does not fit and never gets a chance to recover. A spike, where pressure jumps to red for a few seconds during a launch or an export and returns immediately, describes normal operation and should be ignored.

Two adjustments make the shape easier to see. Activity Monitor's update frequency can be changed under the View menu, and a slower interval smooths out noise that makes every graph look alarming. Leaving the window open on a second display or in a corner for a working morning costs nothing and produces the only evidence that distinguishes a plateau from a sawtooth.

There is a useful test that takes ten seconds. Quit the single largest application in the list and watch the graph rather than the number. If pressure drops to green and stays there, the working set is one application too large. If it barely moves, no single thing is responsible and the total is the problem.

Compression and swap are two different stages

The Memory pane shows both, and they represent different degrees of the same shortage. Compressed memory is handled in RAM, and swap is handled on the disk.

Compressed: The amount of memory that has been compressed to make more RAM available. When your computer approaches its maximum memory capacity, inactive apps in memory are compressed, making more memory available to active apps. Source: support.apple.com

Compression costs processor time and nothing else, which is why it is the first response. A large Compressed figure on a machine that feels fine is a sign the system is managing well, not a sign of trouble.

Swap is the next stage and its cost is different.

Swap Used: The amount of space being used on your startup disk to swap unused files to and from RAM. Source: support.apple.com

The figure itself is less informative than its behaviour. Swap that grew to a few gigabytes during a heavy afternoon and then sat still is history. Swap that is climbing while the pane is being watched is current, and climbing swap with yellow pressure is the combination that produces the stutter when switching between applications, because returning to something that was swapped out means reading it back from the disk first.

Attributing the pressure to something specific

The process list answers this, but only after two changes to how it is read.

The first is to add the Compressed Memory column, which is available by right-clicking the column headers or through the View menu. Sorting by Memory alone shows what is holding the most right now. The compressed column shows what has been pushed out of active RAM, which is often a different set of applications and a better guide to what the session cannot hold.

The second is to expect browsers and other multi-process applications to appear as many rows rather than one. A browser with a dozen web applications open produces a renderer process per site plus separate processes for extensions with background pages. Any single row may look modest while the group is the largest consumer on the machine. Collapsing the view by process hierarchy, or simply reading the rows with the same name together, is necessary before concluding that some other application is at fault.

What usually emerges is that two or three long-lived web applications account for most of it. A mail client holding a long thread list, a chat application with months of scrollback, a board that has been open since Monday. None of them is doing anything wrong. They are just resident, and resident is what the pressure graph measures.

The combinations that come up most often reduce to a short table.

Pressure	Swap behaviour	What it means	Worth acting on
Green, most RAM in use	Flat	Cached files doing their job	No
Brief red spike, returns to green	Flat	An application launching or exporting	No
Yellow sawtooth through the day	Grows slowly	At the edge of capacity, recovering	Only if switching feels slow
Yellow plateau all day	Climbing	Working set larger than available RAM	Yes
Red while the machine feels slow	Climbing	Genuinely short of memory	Yes, including hardware
Yellow with one huge process	Flat	One application, not the machine	Yes, that application

What the numbers do not justify

Memory cleaning utilities and commands that free memory on demand work by forcing the system to discard caches and release pages. The graph responds immediately, which is what makes them convincing. The cache then refills, because the files being cached are the files being used, and the work of refilling it is real work that the machine did not need to do. Nothing about the session got smaller.

Quitting applications at random has a similar problem. It changes the total without addressing which parts of the total were expensive, and the expensive parts are rarely the ones that come to mind. Closing a text editor and keeping eight web applications open moves the number by a rounding error.

Restarting daily is sometimes offered as maintenance. It does clear swap and reset long-lived processes, and a machine that only behaves for an hour after a restart has told you something specific: the daily session, not the uptime, is the cause.

When more memory is the only answer

Red pressure on a plateau, with swap climbing, on a machine doing work that cannot be reduced, is the case where hardware is the answer. Before assuming it can be added, check whether this machine allows it at all.

To learn whether you can add RAM to your Mac, press and hold the Option key, then choose Apple menu > System Information. Under Hardware on the left, click Memory. In the Memory Slots pane, go to Upgradeable Memory to find out whether you can replace or install memory. Source: support.apple.com

On current Apple silicon laptops that pane will not offer an upgrade, because unified memory is fixed at the time of purchase. That makes the arrangement of the working session the only remaining variable on those machines, which is why it is worth getting right rather than treating as a workaround.

Where the arrangement of the session comes in

If the attribution step points at a handful of web applications, the useful change is structural rather than a matter of closing things more often. Applications that have to stay open all day are different from pages opened to read once, and treating them the same is what produces a working set that nobody chose.

Running each application in its own isolated space makes the cost legible, since the process list then names the application instead of the browser. It also makes the set countable, which is the part that matters: an arrangement where eight always-on applications are visible as eight windows gets pruned, and a strip of forty tabs never does. The workspaces page describes how the separation works, and the practical effect on memory is simply that the daily set stops growing without anyone noticing.

What to change first

Watch the graph for a working morning instead of reading it once, because the shape tells you whether the machine is recovering or stuck. If it plateaus in yellow with swap climbing, add the Compressed Memory column, read the browser's rows as a group, and deal with the two or three always-open web applications that account for most of it. If those have to stay open, give each one its own window and its own login, which is the arrangement SpaceDeck is built around on macOS.