2 ms·

The kernel isn't good at handling OOM – to the nearest approximation it just kills whatever is using the most memory, which in my experience is almost always th

The kernel isn't good at handling OOM – to the nearest approximation it just kills whatever is using the most memory, which in my experience is almost always the thing that I least want it to kill. And it does it late enough that everything is broken anyway and the system sits thrashing forever. All that seems to have happened here is that Ubuntu may have rolled out systemd-oomd with some overly-conservative settings, so if we could all avoid having a collective pointless shit-fit about systemd again that would be great.

josephcsible 4y ago
> it just kills whatever is using the most memory, which in my experience is almost always the thing that I least want it to kill. I've had the opposite experience. Usually when I'm out of memory, it's because some single process has gone crazy with memory allocation. Killing it brings the system back to "normal", but killing anything else would just lead to said crazy process gobbling up the newly-freed memory, and then being back to where I started. > And it does it late enough that everything is broken anyway and the system sits thrashing forever. This part I agree with.