Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #247232

Re: Out of memory killer misconfigured?

From <tomas@tuxteam.de>
Newsgroups linux.debian.user
Subject Re: Out of memory killer misconfigured?
Date 2022-04-15 12:20 +0200
Message-ID <Ecrdv-8T4E-7@gated-at.bofh.it> (permalink)
References (2 earlier) <E6pep-53F8-13@gated-at.bofh.it> <E7iDU-5CdC-1@gated-at.bofh.it> <EciDf-8NOj-1@gated-at.bofh.it> <Ecn9T-8Qsj-1@gated-at.bofh.it> <Ecr3P-8T0A-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Fri, Apr 15, 2022 at 11:03:07AM +0100, piorunz wrote:
> On 15/04/2022 06:53, tomas@tuxteam.de wrote:
> > If you want to learn more about that, the Linux MM ("memory
> > management") people have set up a wiki for that:
> > 
> >    https://linux-mm.org/OOM_Killer
> > 
> > Enjoy:)
> > 
> > (and yes, on my box, more memory-hungry processes have a higher
> > /proc/<pid>/oom_score, so they seem to incur a higher risk of
> > being killed. The browser lies somewhat because it spawns quite
> > a few processes, but as a product of the propaganda industry,
> > lying is its second nature;-)
> 
> Yes I understand that from my point of view everything is bad and I am
> not objective.
> However, I see how things are broken and that is indeed obvious.
> I seen before my own eyes how Linux killed KDE session including Xorg
> but left 10x wine's exe processes with 8GB RAM each as a last. Entire
> tree with parent process was using all of the memory that would be 50+
> GB. How this process tree is not having HIGHEST POSSIBLE OOM score and
> is not being killed in first microsecond of OOM situation is beyond my
> understanding.

- At the "low level": you are talking about "process trees".
 Perhaps that's the problem. Perhaps, towards the OOM score,
 all those processes count as individual processes. Note that
 the OOM killer is just the last straw the system grabs to
 try to avoid sinking. Perhaps it's the wrong instrument for
 your case and you need to look into limits, or cgroup memory
 policies.

- At the "higher level": "you see how things are broken" for
 you. You are still (in my opinion) committing the error of
 generalising your problem /before/ you have spent enough
 time investigating it. That might make it more difficult
 finding a satisfying solution :-) Plus, don't assume random
 kernel programmers aren't smart. They usually are. And they
 usually spend quite a bit of effort until a patch of this
 kind goes in.

Cheers
-- 
t

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-03-29 11:40 +0200
  Re: Out of memory killer misconfigured? Sven Hoexter <sven@stormbind.net> - 2022-03-29 12:10 +0200
    Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-03-29 20:40 +0200
      Re: Out of memory killer misconfigured? Tixy <tixy@yxit.co.uk> - 2022-03-30 10:20 +0200
        Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-03-31 19:00 +0200
          Re: Out of memory killer misconfigured? Jonathan Dowland <jon+debian-user@dow.land> - 2022-04-20 12:30 +0200
            Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-04-20 17:30 +0200
              Re: Out of memory killer misconfigured? Jonathan Dowland <jon+debian-user@dow.land> - 2022-04-20 18:20 +0200
                Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-04-20 19:50 +0200
                Re: Out of memory killer misconfigured? David Wright <deblis@lionunicorn.co.uk> - 2022-04-20 20:40 +0200
    Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-03-29 20:50 +0200
      Re: Out of memory killer misconfigured? Greg Wooledge <greg@wooledge.org> - 2022-03-29 21:20 +0200
        Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-03-29 22:10 +0200
          Re: Out of memory killer misconfigured? Greg Wooledge <greg@wooledge.org> - 2022-03-29 22:20 +0200
    Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-03-29 21:00 +0200
      Re: Out of memory killer misconfigured? Nicholas Geovanis <nickgeovanis@gmail.com> - 2022-03-29 21:20 +0200
      Re: Out of memory killer misconfigured? <tomas@tuxteam.de> - 2022-04-01 08:10 +0200
        Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-04-15 03:10 +0200
          Re: Out of memory killer misconfigured? <tomas@tuxteam.de> - 2022-04-15 08:00 +0200
            Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-04-15 12:10 +0200
              Re: Out of memory killer misconfigured? <tomas@tuxteam.de> - 2022-04-15 12:20 +0200
                Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-04-18 22:10 +0200
                Re: Out of memory killer misconfigured? Tim Woodall <debianuser@woodall.me.uk> - 2022-04-19 17:50 +0200
                Re: Out of memory killer misconfigured? <tomas@tuxteam.de> - 2022-04-19 18:10 +0200
                Re: Out of memory killer misconfigured? Nicholas Geovanis <nickgeovanis@gmail.com> - 2022-04-19 22:10 +0200
  Re: Out of memory killer misconfigured? Jonathan Dowland <jon+debian-user@dow.land> - 2022-04-20 12:30 +0200

csiph-web