Re: configurability of OOM killer
От | Tom Lane |
---|---|
Тема | Re: configurability of OOM killer |
Дата | |
Msg-id | 18162.1201910904@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | configurability of OOM killer (Alvaro Herrera <alvherre@commandprompt.com>) |
Ответы |
Re: configurability of OOM killer
Re: configurability of OOM killer Re: configurability of OOM killer Re: configurability of OOM killer |
Список | pgsql-hackers |
Alvaro Herrera <alvherre@commandprompt.com> writes: > This page > http://linux-mm.org/OOM_Killer Egad. Whoever thought *this* was a good idea should be taken out and shot: The independent memory size of any child (except a kernel thread) is added to the score: /* * Processes which fork a lot of child processes are likely * a good choice. We add the vmsize ofthe childs if they * have an own mm. This prevents forking servers to flood the * machine with an endlessamount of childs */ In other words, server daemons are preferentially killed, and the parent will *always* get zapped in place of its child (since the child cannot have a higher score). No wonder we have to turn off OOM kill. regards, tom lane
В списке pgsql-hackers по дате отправления: