From owner-freebsd-stable Sat Mar 10 5:39:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id A3E0437B719 for ; Sat, 10 Mar 2001 05:39:41 -0800 (PST) (envelope-from mvh@ix.netcom.com) Received: from netcom1.netcom.com (lai-ca4c-134.ix.netcom.com [209.110.246.134]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id IAA12595; Sat, 10 Mar 2001 08:39:35 -0500 (EST) Received: by netcom1.netcom.com (Postfix, from userid 1000) id BF1A4113E7A; Sat, 10 Mar 2001 05:27:22 -0800 (PST) From: Mike Harding To: bde@zeta.org.au Cc: stable@FreeBSD.org, mi@aldan.algebra.com In-reply-to: (message from Bruce Evans on Sat, 10 Mar 2001 23:58:51 +1100 (EST)) Subject: Re: load stays at 1 on an idle machine References: Message-Id: <20010310132722.BF1A4113E7A@netcom1.netcom.com> Date: Sat, 10 Mar 2001 05:27:22 -0800 (PST) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have seen this behavior a number of times over the years, but never tracked it down. I even looked at the kernel code which computed the load to see if I could identify anything obvious. I have noticed that when this happes, the load is basically a completely stable value of 1.0 or very close to it, almost like it is in a locally stable state. Didn't look for zombies though - I use junkbuster and it always keeps a few zombies around because the main spawn loop is screwy. (grrr). - Mike Harding Date: Sat, 10 Mar 2001 23:58:51 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org Cc: Mikhail Teterin Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.ORG Precedence: bulk On Fri, 9 Mar 2001, Will Andrews wrote: > On Fri, Mar 09, 2001 at 10:39:53AM -0500, Mikhail Teterin wrote: > > I was running a single instance of SETI@Home, when I observed the load > > of 2. I stopped seti and the load went down to one. It stays there for > > about 20 hours already. The machine is idle: > top(1) doesn't show all stats relevant to the load average. Check > vmstat/systat/iostat/netstat/etc. Perhaps it is the entropy harvester reaping itself ;-). > Besides, the load average is a > worthless metric if you ask me. Erm, it is a fundamental part of the scheduler. The scheduler is b0rked, but not that part of it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message