"The expert described what had happened, in the form of a Haiku:"
The logs were in a mess, But the expert could see, That the database was in distress.
The logs are broken!, Sysadmin sweeps up the leaves, The database cried
It's honestly mind-boggling that we now have tools that even make something like this possible.
(Even though GPT-3 clearly has to read more poetry.)
I've seen a lot of cool / practical uses for GPT-3.
It was trained on the internet, a gigantic repository of half-truths and misinformation, and it has no actual understanding of truth or falsehood.
Ask it for things and you get a plausible-sounding summary, good enough that most people will not fact-check the gibberish it's spewing.
Especially not when you glorify the big pile of automated statistical analysis with the title "AI".
There are plenty of other issues with it, but that'll do for a start.
This isn't a slight against the short-summary technique, which seems very cool.
Details: oom_adj isn't a flag, it's an int which can disable OOM on a per-process-leader basis but can also but can also be used to reduce the "badness" of a process when considering what to kill. Oom_adj is also deprecated and has been replaced by oom_score_adj. The OOM algorithm isn't called RSS. It doesn't seem to have been explicitly named, but the function which performs the key calculation is named oom_badness. This function assigns an integer "badness" to each process. A process' resident set size is an important part of calculating badness, but it's affected by several other factors (what they are depends on kernel version but they include the adjustment parameter). RSS is not (part of) the OOM calculation "by default" -- it's always included unless OOM is disabled entirely. RSS isn't a comparison of reserved physical memory against current virtual size, it's just the amount of RAM currently occupied by a process (i.e. not in swap or on disk). The OOM killer doesn't compare RSS against virtual size. RSS doesn't trigger the OOM killer. RSS isn't an algorithm.
Another interesting aspect of this, of course, is that GPT-3 likely wasn't trained on any specific kernel version, but on a large number of versions depending on which part of the Internet it happened to be reading. This means that it probably can't give a good account of any single version of fast-changing parts of the kernel like the OOM killer.
Source: https://github.com/torvalds/linux/blob/master/mm/oom_kill.c
