From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 9 09:38:54 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4939116A4CF for ; Mon, 9 Feb 2004 09:38:54 -0800 (PST) Received: from digitalme.com (imap.digitalme.com [193.97.97.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37A3C43D1F for ; Mon, 9 Feb 2004 09:38:54 -0800 (PST) (envelope-from dkt@digitalme.com) Received: from dkt [61.10.7.113] by digitalme.com with NIMS ModWeb Module; Tue, 10 Feb 2004 01:38:53 +0800 From: Dung Patrick To: silby@silby.com, Date: Tue, 10 Feb 2004 01:38:53 +0800 X-Mailer: NIMS ModWeb Module X-Sender: dkt MIME-Version: 1.0 Message-ID: <1076348333.b793fda0dkt@digitalme.com> Content-Type: text/plain; charset="BIG5" Content-Transfer-Encoding: quoted-printable cc: freebsd-hackers@freebsd.org Subject: Re: Re: [call for helpers!] Tuning for the Beaver Challenge X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2004 17:38:54 -0000 So you suggested to use the default values for section 2.2.3. I think incre= asing maxsockbuf, and portrange would be helpful. Without testing, it is hard to choose a value for kern.ipc.nsfbufs.=20 For those optionts CPU_FASTER_5X86_FPU through CPU_UPGRADE_HW_CACHE, it is = suggested by an user in the forum. I would like to see the comments from = the mailing list. If those options are dangerous, then don't use them. Yes, I can test things locally. But I don't have too much time... Patrick -----Original Message----- From: Mike Silbersack To: Dung Patrick Date: Mon, 9 Feb 2004 11:12:38 -0600 (CST) Subject: Re: [call for helpers!] Tuning for the Beaver Challenge Bascially everything in section 2.2.3 (/etc/sysctl.conf) is wrong; some values may need tweaking, but changing them blindly will not be helpful. The one setting that I do suggest you keep is: kern.ipc.somaxconn=3D512 (128 may be too low for http testing) The settings from section 2.2.4 will _probably_ be ok, but you'll have to run netstat -m after a benchmarking run to really know. One setting which you'll need to change for the apache2 run is kern.ipc.nsfbufs. Unfortunately, -stable doesn't have any way to tell if you're running out, so you'll have to just guess there. Under -current, netstat -m will tell you what you need to know. Also, you'll probably want to increase KVA_PAGES from 256 to 512 so that the kernel does not run out of memory. Under section 2.2.7, take out the section talking about CPU_FASTER_5X86_FPU through CPU_UPGRADE_HW_CACHE - none of these options is going to help, and it will just increase the likelyhood that something goes wrong. In general, it appears that you can run most of the benchmarks locally, sod= suggest that you do that when trying to decide how to tweak settings. For the threads-related benchmarks (volcanomark and apache2 with worker) start asking for help on the -threads mailing list. This is the one thing that is likely to benefit from tweaking. Mike "Silby" Silbersack On Tue, 10 Feb 2004, Dung Patrick wrote: > Hi > > Beaver Challenge 2004 is coming!. > Details in http://osuosl.org/benchmarks/bc/ > > We are preparing the tuning guide. Definitely we need suggestions and com= ments. > > Please see this forum to view the latest tuning guide: > http://osuosl.org/forums/viewforum.php?f=3D8 > > Attached is a ver0.4 of the tuning guide. > > Regards > Patrick > >