Re: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal

2020-07-02 Thread Alexey Avramov
>What about /usr/lib64/qt5/libexec/QtWebEngineProcess processes? These processes get oom_score_adj=300 out of the box, see https://pastebin.com/AFVU9U8X ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to

Re: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal

2020-07-01 Thread Alexey Avramov
>10% and 5% to 1% and 0% Default values is already changed to 4% (but not more than 400 MiB) and 2% (but not more than 200 MiB). A nonzero threshold helps maintain disk cache and speeds up system recovery after correction. ___ devel mailing list --

Re: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal

2020-07-01 Thread Alexey Avramov
>EarlyOOM being a >userspace process that races with the memory-consuming processes and that >may end up not getting scheduled due to the very impending OOM condition >that it is trying to prevent. earlyoom consumes 1 MiB VmRSS and all memory is locked by mlockall(). earlyoom works pretty

Re: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal

2020-07-03 Thread Alexey Avramov
>It is also unclear that it can prevent full OOM (both >RAM and swap completely full) in all cases Kernel's killer is also cannot prevent full OOM in all cases. earlyoom prevent full OOM (and situations close to OOM) much more effective - faster (selects victim in 5-50ms, monitoring interval

Re: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal

2020-07-03 Thread Alexey Avramov
>it should be disabled so it doesn't kill our software What should people who suffer from the fact that the kernel's OOM killer does not work, and they are forced to hard reboot (and lose unsaved data) the computer when it freezes? This is a serious and very common problem that exists for a

Re: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal

2020-07-05 Thread Alexey Avramov
>Linux handles low memory situations just fine, but it's much better if you >have an appropriately sized swap partition and let the kernel do its job No, by default Linux can hang at low memory condition. Huge swap space will not help you if a leak occurs. With a large swap space, the hang can

Re: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal

2020-07-05 Thread Alexey Avramov
>What software in the default image leads to low memory issues? Web browsers? For example, browsers, electron-based apps, blender, compilation, VM, openings files, opening file manager (once I came across this: when I opened the file manager, an uncontrolled leak occurred somewhere in the

Re: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal

2020-09-12 Thread Alexey Avramov
> how much memory that amounts to in the usual scenarios 700M on F32 without any apps started. Largest file: (207.9M) /usr/lib/locale/locale-archive Files list with its sizes: https://pastebin.com/Hpr6D3Sv Locking even 250M-300M takes good effect. For example, demo:

Re: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal

2020-09-13 Thread Alexey Avramov
> So with > applications started, you might get higher. I think we should protect only basic GUI. On computers with 16G+ RAM locking 1G memory with apps should not be a problem if it helps to improve responsiveness. > Was that with or without swap? It was without swap, but with swap it has the

Re: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal

2020-09-13 Thread Alexey Avramov
> If you actually tried to use the memory it says in MemAvailable, you > may very well already get bad side effects as the kernel needs to > reclaim memory used for other purposes (file caches, mmap'ed > executables, heap, …). Depending on the workload, this may already > cause the system to start