From owner-freebsd-questions Wed Jan 14 17:32:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26792 for questions-outgoing; Wed, 14 Jan 1998 17:32:09 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26710 for ; Wed, 14 Jan 1998 17:31:17 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt2-126.HiWAAY.net [208.147.148.126]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id TAA23198; Wed, 14 Jan 1998 19:31:06 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id TAA06848; Wed, 14 Jan 1998 19:07:53 -0600 (CST) Message-Id: <199801150107.TAA06848@nospam.hiwaay.net> X-Mailer: exmh version 2.0.1 12/23/97 To: efinley@castlenet.com cc: questions@FreeBSD.ORG From: David Kelly Subject: Re: Make world times In-reply-to: Message from efinley@castlenet.com (Elliot Finley) of "Wed, 14 Jan 1998 17:44:14 GMT." <34bcf82d.3063632@castlenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Jan 1998 19:07:53 -0600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk > I am getting a make world time of about 2.5 hours with the complete > 2.2-stable source tree. This is on a PII 233 64M SCSI system. Is > this normal? Is there any way to speed it up? I'm getting almost exactly 2 hours for "make buildworld" on a PPro-200/ 512k with the Bovine rc564 client running also too. Also with 64M. For the filesystem(s) containing /usr/src and /usr/obj try: mount -u -o async /usr My /usr/src is on /usr and /usr/obj is elsewhere. Mounting both async trims about 15 minutes off buildworld and about 15 minutes off installworld. Total CPU time as reported by time(1) is essentially the same for either sync or async. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system.