2 ms·

If you're running it in a VM you might not have all that luxurious RAM. When my Linux VM starts swapping I have to either wait an hour or more to regain contro

• imp0cat 1y ago
  Right, but if it's a VM, it's probably provisioned by something like ansible/terraform? If so, it's quite easy to add an init script that will disable this feature and never have to worry about it again.
• mhitza 1y ago
  What distro are you running? systemd-oomd kills processes a bit quicker than what came before (a couple minutes of a slow, stuttery system). Still too slow for a server you'd want to have back online as quickly as possible. At least now when I run out of memory it kills processes that consume the most memory. A few years back it used to kill my desktop session instead!
  • mnw21cam 1y ago
    Right, that's traditionally been because the X server has typically had a fairly large footprint, and therefore has been very attractive for the oom killer. But in the last 15 years or so, some heuristics have been applied to deliberately discourage the oom killer from killing "important things". I install earlyoom on systems I admin. It prevents the low-memory thrashing by killing things while the system is still responsive, instead of when the system is in a state that means it'll take hours to recover.