4 ms·
I agree. Another issue with Linux is that it provides no way to choose which tasks to kill when you start heavily swapping, and the OOM killer won't do anything
by IshKebab 5y ago
I agree. Another issue with Linux is that it provides no way to choose which tasks to kill when you start heavily swapping, and the OOM killer won't do anything because it still thinks everything is fine. You can't just use the normal UI to kill tasks at that point because it will have slowed to a crawl due to all the swapping.
Back when I used Linux with spinning disks it was much better to disable swap and hope the OOM killer did something sane than to wait for 10 minutes for a terminal to open and eventually give up and hard restart.
Windows handles it much better. You just press ctrl-alt-delete and because the GUI is properly integrated into the kernel it can always react and pause other tasks even if the system is heavily loaded.
- xxs 5y ago>no way to choose which tasks to kill when you start heavily swapping This is false, of course. oom_score_adj, or just read on oom_killer.
- pas 5y agoThat's not a choice, it's a predetermined bias. Anyway, the "real solution" is oomd + PSI (pressure stall information), which can detect when memory is running low and the system is affected.