From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 18:15:07 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C2AD16A4B3 for ; Sun, 28 Sep 2003 18:15:07 -0700 (PDT) Received: from web21104.mail.yahoo.com (web21104.mail.yahoo.com [216.136.227.106]) by mx1.FreeBSD.org (Postfix) with SMTP id 9418144017 for ; Sun, 28 Sep 2003 18:15:06 -0700 (PDT) (envelope-from materribile@yahoo.com) Message-ID: <20030929011506.24823.qmail@web21104.mail.yahoo.com> Received: from [24.228.74.10] by web21104.mail.yahoo.com via HTTP; Sun, 28 Sep 2003 18:15:05 PDT Date: Sun, 28 Sep 2003 18:15:05 -0700 (PDT) From: Mark Terribile To: freebsd-questions@freebsd.org In-Reply-To: <20030928230553.BA55416A510@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: Charles Howse Subject: Re: Comparing buildworld times on twin machines X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2003 01:15:07 -0000 Charles Howse writes: > I have 2 machines on my home network with (almost) > identical hardware. ... The only difference is > that curly has 128 MB ram where larry has only 64. Memory available for caching certainly can make a difference. Remember that FreeBSD uses ALL otherwise uncommitted memory for caching, and so a machine with more memory may do less disk I/O. > They *do not*, however have identical hard drives, > even though each machine has 2 drives, with > /usr/obj on the second drive of each machine. And building things can do a lot of disk I/O, and a lot of directory lookups, especially if you have recursive make(1) operations. > Larry can buildworld in 1 hr 57 mins. It takes > curly 3 hrs 16 mins, even though curly has twice > the ram. > If I watch the compile, with one eye on the disk > activity light, it seems to me that the process is > largely CPU intensive, therefore I would expect > that the buildworld times should be roughly equal. Instead of watching just the disk lights, start up systat 1 -vmstat in a free window or console. Learn what the various indicators mean. You'll probably be able to find your answers there. systat(8) is really an incredible tool for understanding where the system is spending its time, and how. __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com