From owner-freebsd-current  Sun Nov 16 22:24:13 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA15336
          for current-outgoing; Sun, 16 Nov 1997 22:24:13 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA15330
          for <current@FreeBSD.ORG>; Sun, 16 Nov 1997 22:24:10 -0800 (PST)
          (envelope-from hasty@rah.star-gate.com)
Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1])
	by rah.star-gate.com (8.8.8/8.8.5) with ESMTP id WAA01031;
	Sun, 16 Nov 1997 22:24:02 -0800 (PST)
Message-Id: <199711170624.WAA01031@rah.star-gate.com>
X-Mailer: exmh version 2.0gamma 1/27/96
To: Simon Shapiro <Shimon@i-connect.net>
cc: current@FreeBSD.ORG
Subject: Re: make world time???/ 
In-reply-to: Your message of "Sun, 16 Nov 1997 21:52:30 PST."
             <XFMail.971116215230.Shimon@i-Connect.Net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 16 Nov 1997 22:24:01 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

It is "Dyson Time" !!!

Me, I suspect is gcc 8)

I concurr with your figures about kernel build time.


	Cheers,
	Amancio

> 
> Hi Amancio Hasty;  On 16-Nov-97 you wrote: 
> >  
> >  Cool!
> >  
> >  
> >  I am curious as for the make world time on a dual PPro system with 
> >  fast disks. It looks like we are very cpu bound with fast disks.
> >  
> >       Tnks,
> >       Amancio
> 
> I think it bottoms (for a FULL build) at 100 minutes or SO.
> Disk I/O stops being an issue around there.
> Memeory is not a problem either.
> 
> On a P6-200x2, with 256MB of RAM, a DUAL DPT 3334UW, 
> /usr/src/ on a 5x RAID-5 array, /usr/obj on a 8x RAID-0 array,
> DPT with 64MB of RAM, we are just at 84 minutes.
> This is with -pipe, noatime, async, -j8, etc.
> I could not verify putting /tmp /var/tmp on mfs as the system reliably
> crashes.
> 
> The ``disk'' I/O is at about 200-400 I/O per second - about 1/9th of the
> capacity of such a system, memory has over 120MB of free RAM, so we are not
> gaining much.  What I do NOT know, and asked before (maybe I should name
> names :-), is is it CPU saturation, PCI saturation or RAM saturation?
> The system reports 80-95% CPU utilization in kernel, 70-80% in user space.
> 
> I have an AMI Goliath on order.  It is supposed to have tow independant PCI
> busses, on the Orion chipset.  Let's see then.
> 
> Simon
>