Like this, for instance :The size of your swapfile doesn't matter-- it's the rate at which you're accessing it that matters.
There is zero impact on performance if you're pushing data you haven't used for a few minutes (let alone days) out to disk and then reading it back in a few minutes later. The size of your swapfile doesn't matter-- it's the rate at which you're accessing it that matters.
I have a feeling people look at Activity Monitor, see "Swap Used" and feel like that's a failure of some sort. Nothing you're describing sounds like swap intensive activity, its sounds like page caching...
Being a bit more serious—I haven't benchmarked this, and probably should but: Suppose that, for your work, you are repeatedly opening, closing, and reopening many different large documents. Further suppose you have lots of extra RAM (as I usually do). Are these documents cached in RAM such that, when you go to reopen them, they are opened from RAM instead of the SSD, thus enabling these documents to open faster? [Until, of course, you reboot.] And are there any other speed-ups you get from being able to take advantage of a large RAM cache? E.g., if you quit an application, and have lots of available RAM, will MacOS move some application info. to RAM cache so that it can be reopened more quickly?
For instance, between the top and bottom screenshots, I quit every application on my computer (along with all my open files). There was a big decrease in App Memory, but not much decrease in Cached Files, suggesting that the apps as a whole aren't moved to Cache when they are quit (though some smaller app state files might be), but that most of the document files that were previously open were left in cache:
Last edited: