Ananicy VS earlyoom

For anyone using CPU or IO intensive programs, you can also keep using your desktop, with Cachy OS kernel or Bore scheduler/kernel and Ananicy or ananicy-cpp. Happy gentoo user here, compiling for hours while listening to music/browsing without hiccups.

You might want to get ananicy. It's a daemon that automatically sets the niceness values of processes for better realtime performance. Basically sets the priority of processes you probably care about (like your DE/WM) higher than that of those you probably don't (like a compiler).

https://github.com/Nefelim4ag/Ananicy Ananicy (ANother Auto NICe daemon) — is a shell daemon created to manage processes' IO and CPU priorities, with community-driven set of rules for popular applications.

Having taken a look at the daemon, it actually reminds of Ananicy. I'm not familiar with 'Gamemode' so I cannot compare but anyways, this seems to be focused in laptops primarily, something that Tuned isn’t either. It’s going to be a nice thing to have around.

You can enable Ananicy with the command systemctl enable --now ananicy.service so that the service always runs, even after a reboot of the computer. The tool then applies the existing rules (https://github.com/Nefelim4ag/Ananicy/tree/master/ananicy.d/00-default) to various programmes such as Steam. If necessary, you can also create or adapt your own rules.

Check out https://github.com/Nefelim4ag/Ananicy

There is also ananicy, billed as, er, 'another auto-nice demon'.

You might want to get ananicy/nohang, or a system oomd killer to better optimise cpu processes and priorities to prevent this.

If you want to automatize this you can use ananicy,it has rules for each program and when you open a program (a game for example),it applies the nice values and IO bounds automatically,you can modify the .rules and create in case the program you have doesn't exist.

> 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?

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.

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.

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.

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