From owner-freebsd-smp Fri Nov 5 22:44:33 1999 Delivered-To: freebsd-smp@freebsd.org Received: from megadodo.segNET.COM (megadodo.segNET.COM [206.34.181.3]) by hub.freebsd.org (Postfix) with ESMTP id D055E14CAC for ; Fri, 5 Nov 1999 22:44:29 -0800 (PST) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc1a188.bf.sover.net [209.198.80.188]) by megadodo.segNET.COM (8.9.1a/8.8.5) with ESMTP id BAA17226; Sat, 6 Nov 1999 01:40:36 -0500 (EST) Date: Sat, 6 Nov 1999 01:40:37 +0000 (GMT) From: Adam Strohl To: Kevin Street Cc: Mike Smith , freebsd-smp@FreeBSD.ORG Subject: Re: Dual Celeron + FreeBSD? In-Reply-To: <87vh7gux8f.fsf@mired.eh.local> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 5 Nov 1999, Kevin Street wrote: > I really had 2 points: > 1) Dual Celeron's do work pretty well given a good workload I agree, I'm quite happy with mine :) > 2) Your assertion that we need more memory bandwidth to go much faster > on the buildworld - I disagree, or at least I think we have not wrung > all the SMP performance out of build world that we should. One big > problem with make -j N is that it does ok at parallelizing the compile > of large subdirectories with lots of C modules since it starts many > compiles at once. Excellent point, I've noticed this, too, I hope these changes can be eventually commited as this is definatly holding my system back. I see my second CPU go idle for good chunks of time while its linking something. Glad to see someone hacking into the problem. If we fail, we _will_ lose the war -- http://www.mozilla.org/ - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message