Anton Aylward wrote:
On 12/01/2020 12:27, Per Jessen wrote:
Andrei Borzenkov wrote:
12.01.2020 20:13, Per Jessen пишет:
In my experience, the oom killer kills the _best_ process, which is the one that uses the most memory.
Which is not necessary the process that caused OOM and that you want to kill.
Exactly. That's what I was trying to say.
As trivial example - you have long running computation (something with matrices or whatever) using almost all of available memory, but not going to allocate more. You start browser that needs memory and provokes OOM. Which program would you want to kill?
Yep. Very much the situation my customer experienced over Christmas. The right thing would have been to kill off some apache threads, instead mysql got killed ....
Actually this sounds like a situation that could best be managed by using CGROUPS to allocate and constrain resources.
I'll certainly pass it on to the customer, but I doubt it. It is an exceptional situation, essentially a DDoS attack. The best defense was simply to restrict the number of apache threads, second best to add some swap space. -- Per Jessen, Zürich (2.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org