From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail190.messagelabs.com (mail190.messagelabs.com [216.82.249.51]) by kanga.kvack.org (Postfix) with SMTP id 4291D6B0078 for ; Fri, 17 Sep 2010 02:01:13 -0400 (EDT) Subject: Re: Default zone_reclaim_mode = 1 on NUMA kernel is bad for file/email/web servers From: Shaohua Li In-Reply-To: <1284684653.10161.1395434085@webmail.messagingengine.com> References: <1284349152.15254.1394658481@webmail.messagingengine.com> <20100916184240.3BC9.A69D9226@jp.fujitsu.com> <1284684653.10161.1395434085@webmail.messagingengine.com> Content-Type: text/plain; charset="UTF-8" Date: Fri, 17 Sep 2010 14:01:04 +0800 Message-ID: <1284703264.3408.1.camel@sli10-conroe.sh.intel.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: "robm@fastmail.fm" Cc: Christoph Lameter , KOSAKI Motohiro , "linux-kernel@vger.kernel.org" , Bron Gondwana , linux-mm , Mel Gorman List-ID: On Fri, 2010-09-17 at 08:50 +0800, Robert Mueller wrote: > > > > Having very little knowledge of what this actually does, I'd just > > > > like to point out that from a users point of view, it's really > > > > annoying for your machine to be crippled by a default kernel > > > > setting that's pretty obscure. > > > > Thats an issue of the NUMA BIOS information. Kernel defaults to zone > > reclaim if the cost of accessing remote memory vs local memory crosses > > a certain threshhold which usually impacts performance. > > We use what I thought was a fairly standard server type motherboard and > CPU combination, and I was surprised that things were so badly broken > for a standard usage scenario with a vanilla kernel with a default > configuration. > > I'd point out that the cost of a remote memory access is many, many > orders of magnitude less than having to go back to disk! The problem is > that with zone_reclaim_mode = 1 it seems lots of memory was being wasted > that could be used as disk cache. > > > > Yes, sadly intel motherboard turn on zone_reclaim_mode by > > > default. and current zone_reclaim_mode doesn't fit file/web > > > server usecase ;-) > > > > Or one could also say that the web servers are not designed to > > properly distribute the load on a complex NUMA based memory > > architecture of todays Intel machines. > > I don't think this is any fault of how the software works. It's a *very* > standard "pre-fork child processes, allocate incoming connections to a > child process, open and mmap one or more files to read data from them". > That's not exactly a weird programming model, and it's bad that the > kernel is handling that case very badly with everything default. maybe you incoming connection always happen on one CPU and you do the page allocation in that cpu, so some nodes use out of memory but others have a lot free. Try bind the child process to different nodes might help. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org