thrash-protect
earlyoom
| thrash-protect | earlyoom | |
|---|---|---|
| 1 | 60 | |
| 160 | 2,749 | |
| - | - | |
| 10.0 | 8.6 | |
| about 2 years ago | 9 days ago | |
| Python | C | |
| GPL-3.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
thrash-protect
-
earlyoom VS thrash-protect - a user suggested alternative
2 projects | 12 Oct 2023
earlyoom
- Earlyoom – Early OOM Daemon for Linux
- Fedora Workstation 39
-
earlyoom VS thrash-protect - a user suggested alternative
2 projects | 12 Oct 2023
-
Linuxatemyram.com
> The system is not supposed to 'lock up' when you run out of physical RAM. If it does, something is wrong. It might become slower as pages are flushed to disk but it shouldn't be terrible unless you are really constrained and thrashing. If the Kernel still can't allocate memory, you should expect the OOMKiller to start removing processes. It should not just 'lock up'. Something is wrong.
I don't why but locking up is my usual experience for Desktop Linux for many years and distros, and I remember seeing at least one article explaining why. The only real solution is calling the OOMKiller early either with a daemon or SysRq.
> It should not take minutes. Should happen really quickly once thresholds are reached and allocations are attempted. What is probably happening is that the system has not run out of memory just yet but it is very close and is busy thrashing the swap. If this is happening frequently you may need to adjust your settings (vm.overcommit, vm.admin_reserve_kbytes, etc). Or even deploy something like EarlyOOM (https://github.com/rfjakob/earlyoom). Or you might just need more RAM, honestly.
Yeah. Exactly. But as the thread says, why aren't those things set up automatically?
- OOM still a disaster zone
-
Fedora spins
It's not that simple: some defaults may differ, and some features may arrive at different times (if ever). For example, earlyoom has been enabled on Workstation since F32, but the KDE Plasma spin got it one release later.
-
So what exactly do I do if Linux crashes?
Most answers will answer your question, but you can do better and avoid the freezes in the first place. IME almost every time the system froze up and didn't come back in a few seconds it was out of memory. The obvious solution is to add memory, but you can use Early OOM to kill hungry processes if you're running out of memory instead.
- Why is there no reliable way to receive signal when OOM killer decides to kill you
-
What do you do when Linux becomes unresponsive (in a frozen state,mouse clicks or keyboard doesn't work)
It sounds like you're running out of memory though, so if your OS's OOM killer isn't working as well as it should, you can try earlyoom as an alternative.
-
Linux Desktop Environments System Usage (Gnome, KDE, XFCE, LXQT, Cinnamon, Mate)
Swap is indeed supposed to prevent this AFAIK. You can though try some tools like EarlyOOM and see if it helps : https://github.com/rfjakob/earlyoom
What are some alternatives?
bustd - Process killer daemon for out-of-memory scenarios
oomd - A userspace out-of-memory killer
koila - Prevent PyTorch's `CUDA error: out of memory` in just 1 line of code.
nohang - A sophisticated low memory handler for Linux
systemd - The systemd System and Service Manager
le9-patch - [PATCH] mm: Protect the working set under memory pressure to prevent thrashing, avoid high latency and prevent livelock in near-OOM conditions
darling - Darwin/macOS emulation layer for Linux
XMousePasteBlock - Userspace tool to disable middle mouse button paste in Xorg
ZenStates-Linux - Dynamically edit AMD Ryzen processor P-States
latent-diffusion - High-Resolution Image Synthesis with Latent Diffusion Models