From owner-freebsd-hackers@FreeBSD.ORG Thu May 15 13:30:19 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 347B437B401; Thu, 15 May 2003 13:30:19 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22F0943FA3; Thu, 15 May 2003 13:30:17 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from athlon.pn.xcllnt.net (athlon.pn.xcllnt.net [192.168.4.3]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h4FKUGwk068609; Thu, 15 May 2003 13:30:16 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from athlon.pn.xcllnt.net (localhost [127.0.0.1]) by athlon.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h4FKUGml000780; Thu, 15 May 2003 13:30:16 -0700 (PDT) (envelope-from marcel@athlon.pn.xcllnt.net) Received: (from marcel@localhost) by athlon.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h4FKUGnt000779; Thu, 15 May 2003 13:30:16 -0700 (PDT) Date: Thu, 15 May 2003 13:30:16 -0700 From: Marcel Moolenaar To: freebsd-performance@freebsd.org Message-ID: <20030515203016.GB543@athlon.pn.xcllnt.net> References: <20030515123033.GP45118@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030515123033.GP45118@garage.freebsd.pl> User-Agent: Mutt/1.5.3i cc: freebsd-hackers@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 20:30:19 -0000 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. 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". Just a thought, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net