On Wed, Jan 31, 2024, at 11:40 AM, Paul Grosu wrote:


https://github.com/facebookincubator/oomd/

2) Or you can completely disable it:

https://www.cjjackson.dev/posts/what-is-systemd-oomd-how-to-disable-it/

We need bug reports to get it fixed rather than disabling it, if it's causing things to get clobbered that shouldn't be.

The kernel OOM killer is strictly concerned about kernel survival in dramatically low memory situations. It is unconcerned about user space making progress. Hence user space oom managers.

I admit this is probably suboptimal in some cases. Full resource control is a better way of handling the ambiguity whether a program is incorrectly hogging resources versus simply doing its job. Resource control may not obviate a user space oom killer but I think what we really care about is giving a program all the resources it needs, up to the point that the user wants an interactive desktop - and then the kernel needs to (in effect) preempt the resource hungry processes in favor of user-desktop interactivity. Resource control can do this but we don't have everything wired up yet, more work is needed.


--
Chris Murphy