From owner-freebsd-performance@FreeBSD.ORG Fri Dec 23 15:00:07 2011 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 922F01065670; Fri, 23 Dec 2011 15:00:07 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3D2D78FC14; Fri, 23 Dec 2011 15:00:07 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id DF7EB46B09; Fri, 23 Dec 2011 10:00:06 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 6ED65B955; Fri, 23 Dec 2011 10:00:06 -0500 (EST) From: John Baldwin To: freebsd-stable@freebsd.org Date: Fri, 23 Dec 2011 10:00:05 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p8; KDE/4.5.5; amd64; ; ) References: <4EF3C0CE.5040802@zedat.fu-berlin.de> <20111222235846.GA6071@icarus.home.lan> In-Reply-To: <20111222235846.GA6071@icarus.home.lan> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112231000.05712.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 23 Dec 2011 10:00:06 -0500 (EST) X-Mailman-Approved-At: Fri, 23 Dec 2011 15:27:33 +0000 Cc: freebsd-current@freebsd.org, igor@hybrid-lab.co.uk, Alexander Leidinger , freebsd-performance@freebsd.org, "O. Hartmann" , Jeremy Chadwick Subject: Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Dec 2011 15:00:07 -0000 On Thursday, December 22, 2011 6:58:46 pm Jeremy Chadwick wrote: > On Fri, Dec 23, 2011 at 12:44:14AM +0100, O. Hartmann wrote: > > On 12/21/11 19:41, Alexander Leidinger wrote: > > > Hi, > > > > > > while the discussion continued here, some work started at some other place. Now... in case someone here is willing to help instead of talking, feel free to go to http://wiki.freebsd.org/BenchmarkAdvice and have a look what can be improved. The page is far from perfect and needs some additional people which are willing to improve it. > > > > > > This is only part of the problem. A tuning page in the wiki - which could be referenced from the benchmark page - would be great too. Any volunteers? A first step would be to take he tuning-man-page and wikify it. Other tuning sources are welcome too. > > > > > > Every FreeBSD dev with a wiki account can hand out write access to the wiki. The benchmark page gives contributor-access. If someone wants write access create a FirstnameLastname account and ask here for contributor-access. > > > > > > Don't worry if you think your english is not good enough, even some one- word notes can help (and _my_ english got already corrected by other people on the benchmark page). > > > > > > Bye, > > > Alexander. > > > > > > > > > > > > > > > > Nice to see movement ;-) > > > > But there seems something unclear: > > > > man make.conf(5) says, that MALLOC_PRODUCTION is a knob set in > > /etc/make.conf. > > The WiJi says, MALLOC_PRODUCTION is to be set in /etc/src.conf. > > > > What's right and what's wrong now? > > I can say with certainty that this value belongs in /etc/make.conf > (on RELENG_8 and earlier at least). > > src/share/mk/bsd.own.mk has no framework for MK_MALLOC_PRODUCTION, > so, this is definitely a make.conf variable. Eh, normal make variables can go in src.conf as well. They do not have to be listed in bsd.own.mk. World builds include /etc/src.conf whereas every make invocation includes /etc/make.conf via sys.mk. The only reason to use /etc/src.conf is to have a place to put variables only affect make buildworld / buildkernel but do not affect other make invocations. Also, MALLOC_PRODUCTION is generally enabled in a stable branch as part of making the stable branch, there should be no need to set it manually in a stable branch. -- John Baldwin