Date: Wed, 8 Jun 2005 22:35:13 +0200 From: Andreas Klemm <andreas@freebsd.org> To: Sean McNeil <sean@mcneil.com> Cc: FreeBSD amd64 List <freebsd-amd64@freebsd.org> Subject: Re: Top broken in AMD64? Message-ID: <20050608203513.GA2265@titan.klemm.apsfilter.org> In-Reply-To: <1118256882.76070.0.camel@server.mcneil.com> References: <20050608145053.B10686@zoraida.natserv.net> <1118256882.76070.0.camel@server.mcneil.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 08, 2005 at 11:54:42AM -0700, Sean McNeil wrote: > On Wed, 2005-06-08 at 14:52 -0400, Francisco Reyes wrote: > > Building a kernel and top reports 0.0% idle, yet it doesn't show a single > > program with ANY utilization under WCPU or CPU most of the time. > > Ocassionaly it would show up to 20% on WCPU, but for the most part it's 0. > > That is because the processes are not lasting long enough to show in > top. This is perfectly normal behavior and top is not broken. In former time that was different. Unluckily I don't remember when this changed. Even if its not a bug it limits the usefulness of top. I'd say normally you should expect to see what processes within delta t led to 0.0% idle. Can perhaps somebody explain why top nowadays seem to behave differently to lets say 2 years ago ? Andreas /// -- Andreas Klemm - Powered by FreeBSD 5.4 Need a magic printfilter today ? -> http://www.apsfilter.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050608203513.GA2265>