Date: Sun, 15 Oct 2006 23:16:17 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Adrian Chadd <adrian@freebsd.org> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: kernel profiling? Message-ID: <20061016031617.GB1303@xor.obsecurity.org> In-Reply-To: <d763ac660610151953x69a66133v977279ab9c7e20bc@mail.gmail.com> References: <d763ac660610151953x69a66133v977279ab9c7e20bc@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Mon, Oct 16, 2006 at 10:53:36AM +0800, Adrian Chadd wrote: > Hiya, > > Whats the "right" way to grab kernel profiling data these days? > > I've tried using the kernel profiling w/ kgmon and gprof but the top CPU > wasters are the profiling functions themselves, quickly followed by > write_eflags(). I'm not sure this is valid at all. > > I'm running 6-stable on an Athlon 1800XP, so its uniprocessor and > (relatively) slow. I'm hitting the server rather hard with a few thousand > TCP connections a second; I'm trying to figure out where my ~60% of kernel > time and ~35% of interrupt time is going. pmc can be extremely useful although it doesn't do call graphs. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFMvmBWry0BWjoQKURAuCjAKDHos6pk6N+XKmS4EyvDC1OdAz08QCgv8EK 3KKoKLIvXNPlYSw93RcQcW4= =jxxX -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061016031617.GB1303>