3 ms·
Although for different reasons (and different talking points) it reminds me on the discussion about swap (virtual memory / paging file) on windows (and all thos
by SunlitCat 2y ago
Although for different reasons (and different talking points) it reminds me on the discussion about swap (virtual memory / paging file) on windows (and all those "great" guides suggesting to set it to a fixed size or bluntly just to turn it off because "no one needs it anyways").
- Dalewyn 2y agoFixing the page file's size made sense for the time. The page file would have resided on HDDs, having the size fixed meant it would occupy one contiguous chunk of space on the platters thereby maximizing access speed and latency. A page file of variable size would inevitably become fragmented, which manifests as horrible access speed and latency. Nowadays with the page file residing on SSDs this advice isn't relevant anymore, but that doesn't mean it wasn't relevant during its time. As an aside, I still stick to the RAMx1.5=Swap rule because I'm just far too lazy to really optimize it, drive space is cheap now, and I still don't trust Windows to be smart with sizing it. Yes, that means I have a 96GB page file in my Windows 11 machine with 64GB of RAM; yes, it works and I don't care any further. :V
- SunlitCat 2y agoWell, fixed pagefile size are (were) fine if you def. knew for what tasks / applications you use. But for a lot of people (esp. in gaming but not limited to) fixed pagefile sizes caused problems when applications overallocated memory beyond the pagefile size (not necessarily used it, just allocating it was already enough to trip out of memory situation, I think).