On Fri, Jan 10, 2020 at 2:05 AM Lennart Poettering <mzerqung(a)0pointer.de> wrote:
On Mi, 08.01.20 12:24, Chris Murphy (lists(a)colorremedies.com) wrote:
> On Mon, Jan 6, 2020 at 11:09 AM Lennart Poettering <mzerqung(a)0pointer.de>
> > - facebook is working on making oomd something that just works for
> > everyone, they are in the final rounds of canonicalizing the
> > configuration so that it can just work for all workloads without
> > tuning. The last bits for this to be deployable are currently being
> > done on the kernel side ("iocost"), when that's in, they'll
> > oomd (or simplified parts of it) to systemd, so that it's just there
> > and works. It's their expressive intention to make this something
> > that also works for desktop stuff and requires no further
> > tuning. they also will do the systemd work necessary. time frame:
> > half a year, maybe one year, but no guarantees.
> Looks like PSI based oom killing doesn't work without swap. Therefore
> oomd can't be considered a universal solution. Quite a lot of
> developers have workstations with quite a decent amount of RAM,
> ~64GiB, and do not use swap at all. Server baremetal are likewise
> mixed, depending on workloads, and in cloud it's rare for swap to
> We think earlyoom can be adjusted to work well for both the swap and
> no swap use cases.
Isn't rearlyoom also watching the swap metrics only?
No, memory free and swap free, as a percentage. Super simplistic. If
there is no swap, then the percent only applies to MemAvailable.