Oomd Alternatives

oomd reviews and mentions

• Defrag Like It's 1993
  1 project | news.ycombinator.com | 16 Dec 2021

  OOMKiller has a bunch of issues. Its heuristics don't apply well across the wide range of workloads Linux provides (webserver? Database server? build server? desktop client? Gaming machine?), each of which would require its own tuning. (random example: https://lwn.net/Articles/761118/)

  That's why some orgs implemented their own solutions to avoid OOMKiller having to enter the picture, like Facebook's user-space oomd: https://github.com/facebookincubator/oomd

• Paru is building oomd-git package from AUR everytime I run the update command.
  1 project | /r/archlinux | 24 Oct 2021

  I use paru to install/update the softwares on my laptop. I usually update the system twice per week. But recently I've noticed that oomd-git package was showing in the AUR updates everytime I ran the paru command. So, I checked the upstream URL but the main branch shows no new commits since last month. I have no idea why is this happening and weather it's a paru issue or oomd-git issue.

• Holy memory usage, Batman!
  2 projects | /r/jellyfin | 14 Mar 2021

  Additionally, you might want to check this: https://github.com/facebookincubator/oomd

• Systemd 248 RC3: systemd-oomd is now considered fully supported
  3 projects | news.ycombinator.com | 13 Mar 2021

  I think the distinction is that MemoryMax= is just an interface to the cgroupv2 setting, i.e., that rule is implemented inside the kernel and invokes the kernel's OOM killer within a cgroup. The manpage for systemd-oomd says, "systemd-oomd is a system service that uses cgroups-v2 and pressure stall information (PSI) to monitor and take action on processes before an OOM occurs in kernel space."

  It looks like systemd-oomd is related to (based on? from the same people as?) Facebook's oomd https://github.com/facebookincubator/oomd , whose documentation gives a bunch of reasons as to why you would prefer a userspace oomd that takes in PSI data and can be configured to proactively kill misbehaving processes instead of just letting the kernel OOM killer handle it. The major reason is time to recovery: a misbehaving process can cause a system to be so far under pressure that the kernel OOM killer will take a long time to flush things out, but a userspace component can respond in advance with more configurable rules (and more flexibility, since the kernel doesn't believe you're at capacity yet).

• Arch runs out of memory, then crashes
  3 projects | /r/archlinux | 3 Feb 2021

  oomd - developed by facebook and will be default in Fedora 34, it is part of Systemd 247 but still in experimental stage

• A note from our sponsor - SaaSHub
  www.saashub.com | 10 May 2024

  SaaSHub helps you find the best software and product alternatives Learn more →