What Is Memory Compression in Modern Windows — and Why You Should Leave It On

What Windows actually compresses and why

When physical memory runs short, the memory manager has two choices for pages nobody has touched in a while: write them out to pagefile.sys on disk, or compress them and keep the result in a dedicated area of RAM. Compression wins on any normal machine: decompressing a page from memory costs microseconds, while reading it back from disk costs milliseconds — a thousandfold difference, paid every time the app touches that data again. Typical pages compress to about half their size, so 4 GB of cold data fits into roughly 2 GB of RAM.

In Task Manager → Performance → Memory you can see it working in the compressed figure; the Memory Compression process (in Windows 10 it showed up as System and compressed memory) is the system worker that does the packing on behalf of applications. Get-MMAgent in PowerShell confirms whether the feature is active on your machine. The biggest beneficiaries are 8 GB laptops and any system running from a hard drive, where every avoided page read is a genuine saving.

• Cold pages get compressed into a dedicated RAM store instead of hitting the disk
• The typical compression ratio is around 2:1 — 4 GB of cold data occupies about 2 GB
• Task Manager shows it under Memory as compressed; Get-MMAgent reports the flag in PowerShell
• The Memory Compression process is a signed Windows worker, not a virus
• Winners are laptops with little RAM and any HDD-based system — a pagefile on spinning disk is brutal

Why disabling it makes things worse

The advice to turn memory compression off circulates with the same energy as the old "clear your RAM" tips, and it fails the same way: Disable-MMAgent -mc removes the compressed store, so evicted pages go straight to the pagefile. On a machine with 8 GB and a browser with thirty tabs, that means constant disk reads where microseconds of decompression used to be. Free RAM may look prettier in a gadget; the applications lose.

The honest edge cases are narrow. A server with a pinned, measured workload can lose a little throughput to compression CPU on weak cores, and some virtualization setups manage guest memory themselves. On a desktop or laptop — including gaming rigs with plenty of RAM — the default is right: leave it on, and if you suspect it, measure first with Task Manager and Get-MMAgent before flipping a switch you will have to justify later.

Questions and Answers

Read next