Date: Mon, 07 Jan 2008 15:58:53 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: "Vadim Goncharov" <vadim_nuclight@mail.ru> Cc: Peter Jeremy <peterjeremy@optushome.com.au>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, "advocacy@freebsd.org" <advocacy@freebsd.org> Subject: Re: sbrk(2), OOM-killer and malloc() overcommit Message-ID: <86tzlp65si.fsf@ds4.des.no> In-Reply-To: <opt4gojwrp17d6mn@nuclight.avtf.net> (Vadim Goncharov's message of "Sat\, 05 Jan 2008 20\:44\:10 %2B0600") References: <opt4euzyj44fjv08@nuclight.avtf.net> <20080104192820.GM947@server.vk2pj.dyndns.org> <opt4e9q3n14fjv08@nuclight.avtf.net> <20080105011027.GA21334@server.vk2pj.dyndns.org> <opt4gojwrp17d6mn@nuclight.avtf.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"Vadim Goncharov" <vadim_nuclight@mail.ru> writes: > There were case in our town when on heavy loaded web-server apache > processes were dying on memory pressure - aforementioned man said that > was due to overcommit and OOM killer working. Well, technically, it was because the server didn't have enough RAM for the workload it was given. Turning off memory overcommit wouldn't fix that, it would just change the symptoms. I don't know of a single server OS that doesn't overcommit memory. The only difference between them is how they behave once the shit hits the fan. Anyway, as somebody else mentioned, the details are in the archives - if you don't know enough English to find them there, I don't see how having them summarized in English will help. If the language barrier really is a problem, ask someone who speaks your language to help you. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86tzlp65si.fsf>