OOMKiller has a bunch of issues. Its heuristics don't apply well across the wide range of workloads Linux provides (mobile/android? webserver? Database server?

OOMKiller has a bunch of issues. Its heuristics don't apply well across the wide range of workloads Linux provides (mobile/android? webserver? Database server? build server? desktop client? Gaming machine?), each of which would require its own tuning. (more background at https://lwn.net/Kernel/Index/#Memory_management-Out-of-memory_handling https://lwn.net/Kernel/Index/#Memory_management-Out-of-memor...) That's why some orgs implemented their own solutions to avoid OOMKiller having to enter the picture, like Facebook's user-space oomd [1] or Android's LMKD [2] [1] https://github.com/facebookincubator/oomd https://github.com/facebookincubator/oomd [2] https://source.android.com/devices/tech/perf/lmkd https://source.android.com/devices/tech/perf/lmkd