From owner-freebsd-current@FreeBSD.ORG  Sun Dec 26 11:06:05 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5FD3516A4CE
	for <current@freebsd.org>; Sun, 26 Dec 2004 11:06:05 +0000 (GMT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0A9EC43D41
	for <current@freebsd.org>; Sun, 26 Dec 2004 11:06:05 +0000 (GMT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iBQB2mIo058514;
	Sun, 26 Dec 2004 06:02:48 -0500 (EST)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)iBQB2mTx058511;
	Sun, 26 Dec 2004 11:02:48 GMT
	(envelope-from robert@fledge.watson.org)
Date: Sun, 26 Dec 2004 11:02:48 +0000 (GMT)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: Jeff Roberson <jroberson@chesapeake.net>
In-Reply-To: <20041225191637.K60504@mail.chesapeake.net>
Message-ID: <Pine.NEB.3.96L.1041226105947.45272H-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: schedgraph.py
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Dec 2004 11:06:05 -0000


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