2 ms·
I've had the opposite experience on Windows. I always put swap on HDD, because I've been bitten several times by memory leaking applications rendering the entir
by magicalhippo 7y ago
I've had the opposite experience on Windows. I always put swap on HDD, because I've been bitten several times by memory leaking applications rendering the entire OS unusable until the SSD with the swap file ran out of space.
Windows would happily grow the pagefile beyond the limits I had set, and if the allocation loop was tight enough the OS chocked on handling all page faults. As in using literally minutes to respond to keystrokes.
By putting swap on a slow HDD, Windows has plenty of time to service mouse and keyboard input while waiting for the disk to respond, allowing me to kill the offending application before saturating my disk.
I assume this behavior was OK back when computers had very limited memory, and disks were slow anyway. But these days, if a single application wants more than the available memory (physical + pagefile), I'd rather the OS just said no to the application.
- scottlamb 7y agoI don't use Windows, but it sounds like you can't you set limits on how large the swapfile can get? That's crazy! > But these days, if a single application wants more than the available memory (physical + pagefile), I'd rather the OS just said no to the application. I agree.
- magicalhippo 7y agoOh you can set limits. And then Windows will promptly ignore them, at least under certain circumstances. Why I have no idea.