From owner-freebsd-stable Thu Aug 23 9: 7:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from funnel.cisco.com (funnel.cisco.com [161.44.131.24]) by hub.freebsd.org (Postfix) with ESMTP id 2B6FA37B415; Thu, 23 Aug 2001 09:07:17 -0700 (PDT) (envelope-from bmcgover@bmcgover-pc.cisco.com) Received: from bmcgover-pc.cisco.com (root@bmcgover-pc.cisco.com [161.44.149.69]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id MAA18912; Thu, 23 Aug 2001 12:07:16 -0400 (EDT) Received: from bmcgover-pc.cisco.com (bmcgover@localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.11.3/8.11.3) with ESMTP id f7NG45j01008; Thu, 23 Aug 2001 12:04:05 -0400 (EDT) (envelope-from bmcgover@bmcgover-pc.cisco.com) Message-Id: <200108231604.f7NG45j01008@bmcgover-pc.cisco.com> To: freebsd-qa@freebsd.org Cc: freebsd-stable@freebsd.org Subject: top takes excessively long time to start on RC1.... Date: Thu, 23 Aug 2001 12:04:05 -0400 From: Brian McGovern 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 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. The machine is a pretty typical P3 with an Intel card, 3 IDE disks and 2 SCSI disks. systat -vmstat takes ~2 seconds to start (not bad). 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. Subsequent invocations (2nd, 3rd, 4th, etc.) after stopping the first take as long. Parallel invocations take about 55 seconds to start displaying data. 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. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message