From owner-freebsd-current Sun Apr 2 19:55: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 CF1FB37BC7F for ; Sun, 2 Apr 2000 19:55:20 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id VAA75792 for current@freebsd.org; Sun, 2 Apr 2000 21:55:20 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <200004030255.VAA75792@celery.dragondata.com> Subject: Load average calculation? To: current@freebsd.org Date: Sun, 2 Apr 2000 21:55:19 -0500 (CDT) 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'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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message