For a while, most users worked in Mac OS 8.6, 9.0 was new and a beast, and there was also the Public Beta of Mac OS X. So how did we manage memory then?
memory
In extreme cases, excessive use of swap space on an internal SSD could lead to its premature death, and the end of life for that Mac. How could you assess that?
With Unified memory, don’t you simply add the main and graphics memory sizes from your Intel Mac to determine how much your Apple silicon Mac needs?
How to interpret various measurements reported in Activity Monitor, from % CPU to Energy Impact, and how they can be compared across different Macs.
All about memory: different types, Unified Memory, Mach zones and the kernel, and how to manage system memory problems.
With no possibility of memory expansion, and no upgrading of internal storage, you need to specify your M1 Mac correctly. Here’s how.
How can you tell how much memory is being used by the GPU when both CPU and GPU use Unified Memory? Does it matter anyway?
Each additional Safari window increases WindowServer’s memory use by 1.7 MB on an Intel Mac, but 50 MB on an M1 Mac – thirty times more.
Activity Monitor’s Memory view is the perfect place to watch for memory problems, such as a leak. Demonstrated here in macOS 12.0.1 and 12.1.
Is Monterey burning your memory away? Here are two reproducible memory leaks which could explain that, plus two more than might.
The Eclectic Light Company 