The (poor...) way #Linux handles Out Of Memory situations, and the lack of sophisticated application lifecycle management in FOSS toolkits, can make life on #LinuxMobile not so much fun. When memory fills up too much, devices lag and random stuff breaks.

@fakeshell from @furilabs ported #lmkd from Android to "pure" Linux and improved it in many ways. It consumes much less resources than #earlyoom and took my #FLX1 to over 5 days uptime for the first time!

https://github.com/FuriLabs/lmkd

#mobilelinux

“Oom” sounds like a sigh. 🧘

“Earlyoom” sounds like a tea blend. 🫖

https://github.com/rfjakob/earlyoom

#oom_killer #earlyoom

Had some recent experience with #Linux #OOM (out of memory) management. In theory #systemd allows to set a MemoryMax property that would get a service killed if the service uses more that a memory ceiling. In practice I've found that the service is absurdly slowed down while trying to keep memory within limits. And only after a while does the service get killed.

After playing with this and failing to have it do what I wanted, I realised many people say Linux OOM is really bad and that it's best to implement this in userspace.

In the end I've found #earlyoom. It works perfectly. Problem solved.

https://github.com/rfjakob/earlyoom

Hopefully this solves my OOM problems. I got:

• vm.panic_on_oom enabled, so hopefully when I run out of memory, it just kills the VM instead of hanging.
• #Earlyoom installed so it never comes to that.
• #Zram enabled to get just a little more out of it.

I want to avoid uping the VM's ram as long as I can lol

#selfhosting #linux #microblog