From owner-freebsd-current Sat Apr 19 11:30:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA00521 for current-outgoing; Sat, 19 Apr 1997 11:30:53 -0700 (PDT) Received: from heli-fishing.eos.ncsu.edu (heli-fishing.eos.ncsu.edu [152.1.68.52]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA00515 for ; Sat, 19 Apr 1997 11:30:51 -0700 (PDT) Received: (from camattin@localhost) by heli-fishing.eos.ncsu.edu (8.8.4/EC02Jan97) id SAA41724; Sat, 19 Apr 1997 18:28:57 GMT Message-Id: <199704191828.SAA41724@heli-fishing.eos.ncsu.edu> Subject: Re: Speed deamons: How to build a build box? To: paul@originat.demon.co.uk (Paul Richards) Date: Sat, 19 Apr 1997 14:28:56 -0400 (EDT) Cc: skynyrd@opus.cts.cwu.edu (Chris Timmons), imp@village.org (Warner Losh), current@freebsd.org In-Reply-To: <87lo6fs3xn.fsf@originat.demon.co.uk> from "Paul Richards" at Apr 19, 1997 11:27:32 AM From: camattin@ncsu.edu (Chris A. Mattingly) Reply-To: camattin@ncsu.edu X-Mailer: ELM [version 2.5 PL0b1/POP] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Paul Richards wrote the following about "Re: Speed deamons: How to build a build box?" on Sat Apr 19 06:27:32 1997 > > Chris Timmons writes: > > > My -current build machine at the moment is a pro200, 32mb of EDO and one > > f/w disk on a 3940. With async /usr, CFLAGS -pipe -0, no eBones or secure > > and NOMANCOMPRESS I was building in about 1:41 yesterday afternoon. > > Hmm, it can't be that i/o bound then. > > My P100, with 64Mb and a fast/wide Atlas on a 2940 takes 5 hours to do > a make world. > > I do a bit more than you, I have > CFLAGS= -O2 -m486 -pipe > > and I build the whole lot. If it was a strictly i/o bound process my > P100 wouldn't do so badly since everything else is comparable or > better than your PPro200. FYI, I have a P133, 2940, SEAGATE ST32151N, 64 Megs EDO, and a make world took 4:18:37 .. this included compressing the man pages, eBones, etc, and also cleaning out my last build. -Chris -- Chris Mattingly | My views are not necessarily those of my employers camattin@ncsu.edu | NC State University/ITECS | "Good programmers write good code; great Systems Programmer | programmers 'borrow' good code." -- Mike Gancarz