From owner-freebsd-hackers@FreeBSD.ORG Thu May 15 14:26:24 2003 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 61FDA37B401; Thu, 15 May 2003 14:26:24 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A06F43F93; Thu, 15 May 2003 14:26:21 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (localhost [127.0.0.1]) by haldjas.folklore.ee (8.12.3/8.11.3) with ESMTP id h4FLQJ6U093669; Fri, 16 May 2003 00:26:19 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost)h4FLQJcr093666; Fri, 16 May 2003 00:26:19 +0300 (EEST) Date: Fri, 16 May 2003 00:26:19 +0300 (EEST) From: Narvi To: Marcel Moolenaar In-Reply-To: <20030515203016.GB543@athlon.pn.xcllnt.net> Message-ID: <20030516002105.K40030-100000@haldjas.folklore.ee> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: freebsd-performance@freebsd.org Subject: Re: Optimizations. 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: Thu, 15 May 2003 21:26:24 -0000 On Thu, 15 May 2003, Marcel Moolenaar wrote: > On Thu, May 15, 2003 at 02:30:33PM +0200, Pawel Jakub Dawidek wrote: > > Hello hackers... > > > > IMHO optimization in FreeBSD's code has too low priority. > > Maybe is time to think about some 'optimiztion team' creation? > > I think I don't want to see this happen based on professional > experience. My biggest concern is that it becomes a crusade. > For if your focus is performance, you pretty much loose track > of everything else. If not, then obviously you haven't been > focussing. > Well, supposedly any such team would need to start by creating a set of tools and benchmarks that could be used to quantify perfomance, get buy-in from the project that these give good measures (iterate until done) and then set up a bunch of machines to track there are no regressions? Followed by then starting to work towards eliminating problems 8-) > Don't get me wrong. Optimizing is a good thing, when done at the > right time for the right reasons and in the right way. Having > an optimization team created out of thin air can only lead to > round-table discussions that boil down to "Hi, I'm Marcel. I like > to optimize small objects" and before you know it all hell breaks > loose for a barely measurable performance change. > > If you set yourself some simple goals and keep it high-level, then > we can all get used to the idea and we will probably find other > opportunities while we go. The end result can be much the same as > you try to achieve now, except that it has a bigger chance to be > integrated rather than some weird bunch on the side that plays > with compiler options "and shit". nah, don't be too hard on them. they are volunteering for a large amount of hard work 8-) > > Just a thought, > > -- > Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net >