Date: Sun, 26 Dec 2004 11:02:48 +0000 (GMT) From: Robert Watson <rwatson@freebsd.org> To: Jeff Roberson <jroberson@chesapeake.net> Cc: current@freebsd.org Subject: Re: schedgraph.py Message-ID: <Pine.NEB.3.96L.1041226105947.45272H-100000@fledge.watson.org> In-Reply-To: <20041225191637.K60504@mail.chesapeake.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 25 Dec 2004, Jeff Roberson wrote:
> To use the tool, you will need to define KTR_SCHED in KTR_COMPILE and
> KTR_MASK. I'd also bump entires up to 32768 or larger so you can grab a
> few seconds of data. Run your workload, and then capture the data with
> 'ktrdump -ct > ktr.out'. Then you simply run python schedgraph.py
> ktr.out. This requires a recent version of python and
> ports/x11-toolkits/py-tkinter.
Great!
For those who need a little more hand-holding getting KTR running, here's
a URL to try:
http://www.watson.org/~robert/freebsd/netperf/ktr/
It's been my hope people would start producing more post-processing tools
-- KTR can collect some really great data that's just sitting there
waiting to be mined. I'd be interested in seeing post-processing tools
for locking as well. This looks like a great tool that will be really
helpful in understanding behavior and performance.
Thanks!
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org Principal Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1041226105947.45272H-100000>