From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 31 19:23:36 2009 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9393106566C for ; Fri, 31 Jul 2009 19:23:36 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 41F378FC0C for ; Fri, 31 Jul 2009 19:23:36 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 20686 invoked by uid 399); 31 Jul 2009 18:56:52 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 31 Jul 2009 18:56:52 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4A733E72.5040607@FreeBSD.org> Date: Fri, 31 Jul 2009 11:56:50 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.22 (X11/20090729) MIME-Version: 1.0 To: Steven Hartland References: <200907310919.57775.david@vizion2000.net> <0C3FFA484EC8423AB26C13C6737C8533@multiplay.co.uk> <200907311333.53815.david@vizion2000.net> <1518B86CFB8242F8B605034460287EB1@multiplay.co.uk> In-Reply-To: <1518B86CFB8242F8B605034460287EB1@multiplay.co.uk> X-Enigmail-Version: 0.95.7 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: amd64@freebsd.org Subject: Re: Taking full advantage of Intel Quad Core with Freebsd 7.2p2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jul 2009 19:23:37 -0000 Steven Hartland wrote: > #2 Not sure portupgrade in 7.2 supports -j properly yet, I know there's > been some recent work in that area not sure who far its got. The ports infrastructure already supports this, but you have to add the following option to your /etc/make.conf file: FORCE_MAKE_JOBS= true You will occasionally run into ports that don't build successfully with this option, so you can overcome that per port by doing 'make -DMAKE_JOBS_UNSAFE' for that port. It would be a big help to the community if you could report any ports you run into that problem with so that they can be marked in the Makefile. For building the world if you want the system to be responsive while you're building a good rule of thumb for -j is " -1". If you want maximum speed and don't care about using the system while it builds then " +1" will get it done a little faster. Values much higher than that are not likely to increase speed much, mostly due to the fact that you'll get IO-bound sooner than later. hth, Doug -- This .signature sanitized for your protection