From owner-freebsd-current Mon Apr 3 10:30:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 239FD37B539 for ; Mon, 3 Apr 2000 10:30:30 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id KAA09185; Mon, 3 Apr 2000 10:19:02 -0700 (PDT) Message-Id: <200004031719.KAA09185@implode.root.com> To: Matthew Dillon Cc: Kevin Day , current@FreeBSD.ORG Subject: Re: Load average calculation? In-reply-to: Your message of "Sun, 02 Apr 2000 20:49:10 PDT." <200004030349.UAA52843@apollo.backplane.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 03 Apr 2000 10:19:02 -0700 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. It's always been that way in BSD. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message