From owner-freebsd-qa Thu Aug 23 11:45:39 2001 Delivered-To: freebsd-qa@freebsd.org Received: from guru.mired.org (okc-94-248-46.mmcable.com [24.94.248.46]) by hub.freebsd.org (Postfix) with SMTP id 8FCF337B403 for ; Thu, 23 Aug 2001 11:45:33 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 81152 invoked by uid 100); 23 Aug 2001 18:45:23 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15237.20291.380638.888721@guru.mired.org> Date: Thu, 23 Aug 2001 13:45:23 -0500 To: Brian McGovern Cc: freebsd-qa@freebsd.org, freebsd-stable@freebsd.org Subject: Re: top takes excessively long time to start on RC1.... In-Reply-To: <200108231604.f7NG45j01008@bmcgover-pc.cisco.com> References: <200108231604.f7NG45j01008@bmcgover-pc.cisco.com> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Brian McGovern types: > I've run in to a rather disturbing problem. > > When running a fresh install of 4.4RC1 (not an upgrade), I try to run top. It > takes approximately 1 minute, 29 seconds to begin to display data. FWIW, I've got a fresh install from the 4.4RC1 ISO. top displays the initial process list instantly, and starts displaying and updating system information in ~2 seconds. > systat -vmstat takes ~2 seconds to start (not bad). More like ~4 here. > The machine is a pretty typical P3 with an Intel card, 3 IDE disks and 2 > SCSI disks. Mine's a K6 on a VIA chipset, with 2 IDE disks and 2 IDE CDROMS, but only one of the disks is actually used. > With multiple windows open, it appears that starting top isn't bogging > the system down (it stays mostly idle). There are no more/less interrupts, > top and systat don't show anything becoming a CPU hog, no drop in memory, etc. I don't have X installed on the machine. You might try testing things from a console. > In looking at the top display, it appears (when running two) that one is in > the RUN state, and the other in the select state. This may be a clue. Mine does the same. When top collects the process information to display, it's running, hence it's going to be in the RUN state. When it's not updating, it's sitting waiting for a command or the timer to run out - which is what select is used for. So that seems natural as well. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message