Date: Thu, 23 Aug 2001 12:40:27 -0400 From: Brian McGovern <bmcgover@cisco.com> To: Peter Pentchev <roam@ringlet.net> Cc: Mike Tancsa <mike@sentex.net>, freebsd-qa@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, bmcgover@bmcgover-pc.cisco.com Subject: Re: top takes excessively long time to start on RC1.... Message-ID: <200108231640.f7NGeRj01165@bmcgover-pc.cisco.com> In-Reply-To: Your message of "Thu, 23 Aug 2001 19:29:56 %2B0300." <20010823192956.E503@ringworld.oblivion.bg>
next in thread | previous in thread | raw e-mail | index | archive | help
top -u brings it down to about 40 seconds, on average (max was ~42, min ~38), 6 run sample. Peter is right. This is 'stock' from the 4.4RC1 ISO. I'll be able to collect some more data when I get home this evening from my other test machine. I'll be able to [dis]prove whether its machine specific, I'll be able to play with code and/or build it to profile it, and if I track it in to the kernel, I'll be able to slap a debugger on it. -Brian > On Thu, Aug 23, 2001 at 12:23:15PM -0400, Mike Tancsa wrote: > > > > What if you start it with top -u ? > > > > Also, did you in make.conf adjust > > > [snip] > > #TOP_TABLE_SIZE= 101 > > He said it was a fresh 4.4RC1 install, no recompilation; so any make.conf > adjustments would make no difference. > > G'luck, > Peter > > -- > I had to translate this sentence into English because I could not read the o riginal Sanskrit. > > > At 12:04 PM 8/23/01 -0400, Brian McGovern wrote: > > >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 tak e 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. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200108231640.f7NGeRj01165>