From owner-freebsd-stable Thu Dec 13 10: 1:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 9EE6B37B41A for ; Thu, 13 Dec 2001 10:01:05 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 13 Dec 2001 18:01:04 +0000 (GMT) To: Holtor Cc: stable@freebsd.org Subject: Re: Load Averages In-Reply-To: Your message of "Thu, 13 Dec 2001 09:21:08 PST." <20011213172108.10411.qmail@web11606.mail.yahoo.com> Date: Thu, 13 Dec 2001 18:01:03 +0000 From: Ian Dowse Message-ID: <200112131801.aa19310@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011213172108.10411.qmail@web11606.mail.yahoo.com>, Holtor writes: >I still fail to see why my systems loads went from >1.50 - 2.00. There's over 250 processes constantly >running in "select" state. Loads are now almost always >0.00 and sometimes touching 0.10 The changes to the load average calculation only added jitter to the timing of samples; the algorithm used to compute the load average from the samples is still the same. Could you post a `top' screen shot from the server in question? (make sure to leave top running for long enough to get the %idle etc lines filled in). Is it possible that the processes spend the vast majority of the time sleeping in select(), but that previously their run periods were often synchronised with the samples used to calculate the load average, or maybe it was system processes such as bufdaemon whose run period was synchronised with the samples? If so, then maybe the old loads around 2.0 were simply wrong. In general the %idle figure in top should be close to 100% if the load is close to 0, so that is worth checking too. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message