On Tue, Jan 7, 2020 at 11:23 am, Kamil Paral <kparal(a)redhat.com> wrote:
In your example you forget that swap needs to filled almost to full
for early-oom to start reacting. That takes time during which the
system responsibility is abysmal. The UX difference happens only
after you've already suffered through a serious responsivity
degradation, and the only difference is the end state, *if* you've
managed to wait long enough for early-oom to kick in (which happens
earlier than kernel oom and with better results about which process
gets killed, according to Chris).
Right, we understand this. earlyoom (or a systemd-level OOM solution)
is only half the solution. The other half will be fixing swap. That
will probably require (a) reducing the amount of swap created by
anaconda, and/or (b) swap on zram.