a big advantage of 32-bit executables is they die with allocation failure instead of sending a machine into swapping hell change my mind
-
-
Can use a swapfile rather than a swap partition though. Have 64GB of memory and an 128GB swapfile for hibernation via apcupsd when the UPS has gotten below the 5% power threshold. It never uses the swap in regular use even without tuning anything, so it doesn't really matter.
-
Swap on an NVMe drive is perfectly usable anyway. It wouldn't grind the machine to a halt if it started using it. It would be substantially slower, but these things have fairly insane specs: https://www.samsung.com/us/computing/memory-storage/solid-state-drives/ssd-960-pro-m-2-2tb-mz-v6p2t0bw/ … It'd probably get throttled without good M.2 cooling though.
-
Sure it would, just because Linux's swap code paths are so bad. Even swap on a MTD backed by DDR DRAM causes the system to grind to a halt if memory pressure gets so high that each access has a significant chance of page fault.
-
Haven't had that experience. Doesn't zram, etc. get treated as swap too?
-
I think so but I'm not sure. Again the problem is thrashing, which only happens when you've actually allocated and tried to make heavy use of a lot more memory than available physical ram.
End of conversation
New conversation -
-
-
Or more precisely, adding swap would not add to commit limit in a way you can't turn off, so you could have swap without it actually being usable for satisfying allocation, just for hibernation.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
So many truth flakes in this thread no fight just love ok
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.