nohang
earlyoom
nohang | earlyoom | |
---|---|---|
29 | 61 | |
1,056 | 2,959 | |
- | - | |
4.3 | 8.0 | |
10 months ago | 8 days ago | |
Python | C | |
MIT License | 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.
nohang
-
There is an oom kill count in Linux
For desktop use, nohang does what the name says.
https://github.com/hakavlad/nohang
- Rare question
- Zswap vs zram in 2023, what's the actual practical difference?
-
Why is systemd-oomd still a thing
Personally I thought https://github.com/hakavlad/nohang worked pretty well, and it'll also notify the user if it's about to start killing things, but I haven't bothered to install it in fedora. I did tweak the systemd-oomd config to be less aggressive though.
-
Arch linux randomly freezes, especially when playing a youtube video or performing other video-related workload
SOLUTION: After struggling with this nightmarish unpredictable kernel panic for two weeks, I confirmed nohang is capable of stopping this problem for real.
- Hakavlad / nohang – A sophisticated low memory handler for Linux
-
Релиз ядра Linux 6.1
посмотри https://github.com/hakavlad/nohang/issues/122
-
How do i install packages in ZORIN OS
I'm trying to install this app called " nohang" for memory problems. https://github.com/hakavlad/nohang i wasn't sure which type zorin is based on.
-
Am I doing RAM wrong?
Thanks. Looking into this as well. Further digging in this sub over the past couple days have brought up earlyoom as well as https://github.com/hakavlad/nohang as interesting things to pursue.
-
Distro with best ram management on 8gb of memory?
Sounds like the complaints indicated on nohang's repo. I also have low memory. nohang and zram make mine work better than macs/wins with higher memory.
earlyoom
-
Building a faster, smarter, Chromebook experience with the best of Google
EarlyOOM [1] could help with that quite a lot. Not to sure about using it on chromebooks, but linux got quite a bit more usable because of it.
[1] https://github.com/rfjakob/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.
What are some alternatives?
oomd - A userspace out-of-memory killer
Ananicy - Ananicy - is Another auto nice daemon, with community rules support (Use pull request please)
systemd - The systemd System and Service Manager
Ananicy Cpp - A full, event-based rewrite of Ananicy made in C++ for better performance.
darling - Darwin/macOS emulation layer for Linux
prelockd - Lock executables and shared libraries in memory to improve system responsiveness under low-memory conditions
XMousePasteBlock - Userspace tool to disable middle mouse button paste in Xorg
le9-patch - [PATCH] mm: Protect the working set under memory pressure to prevent thrashing, avoid high latency and prevent livelock in near-OOM conditions
systemd-swap - Script for creating hybrid swap space from zram swaps, swap files and swap partitions.
ZenStates-Linux - Dynamically edit AMD Ryzen processor P-States