From owner-freebsd-questions Thu Apr 2 12:03:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26797 for freebsd-questions-outgoing; Thu, 2 Apr 1998 12:03:03 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from proxy4.ba.best.com (root@proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26780 for ; Thu, 2 Apr 1998 12:02:49 -0800 (PST) (envelope-from kmayer@bitwrangler.com) Received: from shell7.ba.best.com (kmayer@shell7.ba.best.com [206.184.139.138]) by proxy4.ba.best.com (8.8.8/8.8.BEST) with SMTP id MAA18128 for ; Thu, 2 Apr 1998 12:00:35 -0800 (PST) Date: Thu, 2 Apr 1998 12:00:34 -0800 (PST) From: Ken Mayer X-Sender: kmayer@shell7.ba.best.com To: freebsd-questions@FreeBSD.ORG Subject: 2.2.2 --> 2.2.5 yields 50% performance penalty on builds Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I build FreeBSD nightly on a 200Mhz Pentium II, 64M system. When I upgraded from 2.2.2 to 2.2.5 my build times went from a little more than 90 minutes to almost 5 hours. My file server is a Network Appliance box and both are connected on a fast ethernet hub. I am using amd for automounting (e.g. /net/builds). The system seems to be processing an excessive amount of interrupts on the PCI ethernet card and an examination of tcpdump shows a lot of NFS access (stat) calls. Any thoughts on what happened between 2.2.2 and 2.2.5? Ken -- Ken Mayer : In dwelling, live close to the ground. Global Village Idiot : In thinking, keep to the simple. 408/605.1354 (voice/v-mail/pager) : In conflict, be fair and generous. kmayer@bitwrangler.com : In governing, don't try to control. S/V Wishful Thinking : In work, do what you enjoy. '78 Mariner Centaur 34 : In family life, be completely present. http://www.bitwrangler.com/wt/ : -- Tao Te Ching To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message