lkml.org 
[lkml]   [2009]   [Oct]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Memory overcommit
On Wed, 28 Oct 2009, Vedran Furac wrote:

> > Those are practically happening simultaneously with very little memory
> > being available between each oom kill. Only later is "test" killed:
> >
> > [97240.203228] Out of memory: kill process 5005 (test) score 256912 or a child
> > [97240.206832] Killed process 5005 (test)
> >
> > Notice how the badness score is less than 1/4th of the others. So while
> > you may find it to be hogging a lot of memory, there were others that
> > consumed much more.
> ^^^^^^^^^^^^^^^^^^^^^
>
> This is just wrong. I have 3.5GB of RAM, free says that 2GB are empty
> (ignoring cache). Culprit then allocates all free memory (2GB). That
> means it is using *more* than all other processes *together*. There
> cannot be any other "that consumed much more".
>

Just post the oom killer results after using echo 1 >
/proc/sys/vm/oom_dump_tasks as requested and it will clarify why those
tasks were chosen to kill. It will also show the result of using rss
instead of total_vm and allow us to see how such a change would have
changed the killing order for your workload.

> Thanks, I'll try that... but I guess that using rss would yield better
> results.
>

We would know if you posted the data.


\
 
 \ /
  Last update: 2009-10-28 21:13    [W:0.128 / U:0.820 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site