2026-09-22 10:58 UTC
The OOM killer has a much smarter heuristic to deprioritise processes which are being actively used.
Whivh is ehy yoi’re stuck for 2 minutes until it’s done in low-memory. And why i use earlyoom.
(and why yet another systemd-somethingd? Free the service!)
Replies (1)
-
@FishFace@piefed.social 2026-09-22 11:04
Do you actually know that the decision-making takes a long time? I would have assumed that it’s pretty quick as it doesn’t need to access much, and what it does need to access should mostly be staying in RAM even when thrashing. But I don’t know that for sure. I had assumed that essentially all the delay was other things happening very slowly, allocating more memory byte by byte before an actual OOM condition was met.