From owner-freebsd-current Sun Apr 2 20:49:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 71A0737B5D4 for ; Sun, 2 Apr 2000 20:49:22 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA52843; Sun, 2 Apr 2000 20:49:10 -0700 (PDT) (envelope-from dillon) Date: Sun, 2 Apr 2000 20:49:10 -0700 (PDT) From: Matthew Dillon Message-Id: <200004030349.UAA52843@apollo.backplane.com> To: Kevin Day Cc: current@FreeBSD.ORG Subject: Re: Load average calculation? References: <200004030255.VAA75792@celery.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm not sure if this is -current fodder or not, but since it's still :happening in -current, I'll ask. : :We recently upgraded a server from 2.2.8 to 4.0(the same behavior is shown :on 5.0-current, too). Before, with the exact same load, we'd see load :averages from between 0.20 and 0.30. Now, we're getting: : :load averages: 4.16, 4.23, 4.66 : :Top shows the same CPU percentages, just a much higher load average for the :same work being done. Did the load average calculation change, or something :with the scheduler differ? Customers are complaining that the load average :is too high, which is kinda silly, since 4.0 seems noticably faster in some :cases. : :Any ideas? : :Kevin 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. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message