From owner-freebsd-current Sun Apr 2 22:56:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id CC94F37BD63 for ; Sun, 2 Apr 2000 22:56:20 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id AAA76127; Mon, 3 Apr 2000 00:56:03 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <200004030556.AAA76127@celery.dragondata.com> Subject: Re: Load average calculation? To: wc.bulte@chello.nl Date: Mon, 3 Apr 2000 00:56:03 -0500 (CDT) Cc: toasty@dragondata.com (Kevin Day), dillon@apollo.backplane.com (Matthew Dillon), current@FreeBSD.ORG In-Reply-To: <20000403075130.B5528@yedi.wbnet> from "Wilko Bulte" at Apr 03, 2000 07:51:31 AM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I believe the load average was changed quite a while ago to reflect not > > > only runnable processes but also processes stuck in disk-wait. It's > > > a more accurate measure of load. > > > > Ahh, and since nearly everything is done on this system via NFS, I can > > imagine that several things are waiting for NFS responses. > > > > It's probably more accurate, but from a PR standpoint it makes it "look" > > like FreeBSD is choking under the load, when it really isn't. Or am I the > > only one that even cares about this? :) > > What does the man page for 'w' say about it? At least the change should be > reflected there I guess. getloadavg(3)(which 'w' and 'uptime' use) says: The getloadavg() function returns the number of processes in the system run queue averaged over various periods of time. The 'w' and 'uptime' manpages really don't mention anything relevant. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message