From owner-freebsd-questions@FreeBSD.ORG Thu Aug 10 16:24:34 2006 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC73D16A4DE for ; Thu, 10 Aug 2006 16:24:34 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D14C43D72 for ; Thu, 10 Aug 2006 16:24:32 +0000 (GMT) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.4) with SMTP id CAA07388; Fri, 11 Aug 2006 02:23:56 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 11 Aug 2006 02:23:55 +1000 (EST) From: Ian Smith To: Chuck Swiger In-Reply-To: <44DB0FC0.1010705@mac.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: questions@freebsd.org Subject: Re: Top not showing cpu usage even remotely accurately X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2006 16:24:35 -0000 On Thu, 10 Aug 2006, Chuck Swiger wrote: > Ian Smith wrote: > > But since running 5.x (5.5-STABLE since 1st Aug) top can show 0.0% idle > > but the cpu usages shown don't add up to much of a fraction of 100%. > [ ... ] > > Any ideas why top hasn't much of a clue about what's consuming cpu? > > Sure, if you're running a parallel make, that will be starting up lots of > short-lived compiler processes which exit quickly; top can only display the > CPU load for those processes which are still running at the time it samples > the system. Spot on, thanks Chuck. lastcomm showed a couple of thousand processes run per minute during several hours of 'make index'; /var/account/acct was nearly 10MB for that time. Only one gcc but lots of sh, perl, grep, awk, sed and such each running < 1 second, being a texty sort of job. Cheers, Ian