Date: Mon, 07 Aug 2000 21:27:12 -0700 From: Mike Smith <msmith@freebsd.org> To: Dennis <dennis@etinc.com> Cc: hackers@freebsd.org Subject: Re: FreeBSD belly up with big config Message-ID: <200008080427.VAA08691@mass.osd.bsdi.com> In-Reply-To: Your message of "Mon, 07 Aug 2000 21:24:01 EDT." <Version.32.20000807130801.01d386a0@etinc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> >> It seems that there is substantial overhead just scanning interfaces for > >> some routine maintenance...is there any hope of alleviating this deboggle? > > > >Probably. Without some idea of what's actually happening, though, it's a > >little hard to point a finger and say "look here". > > > >A profiling dump of the system when idle would be very illuminating, as > >it'd give you a good idea of what's actually going on to use so much CPU > > How do I do this in 4.1? I have a test bed set up that demonstrates the > problem. Config your kernel with '-pg', build and install. (See config(8)) Low-resolution profiling should be fine. Boot the new kernel, and when it's running use kgmon to grab a profiling dump for, say, 30 seconds. Then use gprof to translate the dump into readable output; at this point the flat profile is a good place to start to get a feel for where the code is busiest. Hope this helps. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008080427.VAA08691>