1 iowatcher graphs the results of a blktrace run. It has a few different modes:
3 * Graph the result of an existing blktrace
7 * Start a new blktrace and a benchmark run
11 -d controls which device you are string. You can only trace one device
12 at a time for now. It is sent directly to blktrace
14 -t controls the name of the blktrace file. iowatcher uses a dump from
15 blkparse, so -t tries to guess the name of the corresponding
16 per CPU blktrace data files if the dump file doesn't already exist.
18 If you want more than one trace in a given graph, you can specify
21 -l Sets a label for a trace file. The labels are added in the same
22 order the trace files are added.
24 -T Set a title for the graph. This goes at the top of the image.
26 -o output filename. The default is trace.svg. iowatcher is
27 only able to create svg for now.
29 -r control the duration in seconds for the rolling average.
30 iowatcher tries to smooth out bumpy graphs by averaging the
31 current second with seconds from the past. Longer numbers here
32 give you flatter graphs.
34 -O add a single graph to the output. By default all the graphs
35 are included, but with -O you get only the graphs you ask for.
36 -O may be used more than once.
38 -N remove a single graph from the output. This may also be used more
41 Choices for -O and -N are:
42 io, tput, latency, queue_depth, iops
46 # generate graph from the existing trace.dump
47 iowatcher -t trace.dump -o trace.svg
50 iowatcher -t trace.dump -o trace.svg -N io
52 # only graph tput and latency
53 iowatcher -t trace.dump -o trace.svg -O tput -O latency
55 # generate a graph from two runs, and label them
56 iowatcher -t ext4.dump -t xfs.dump -l Ext4 -l XFS -o trace.svg
58 # Run a fio benchmark and store the trace in trace.dump
59 # add a title to the top. Use /dev/sda for blktrace
60 iowatcher -d /dev/sda -t trace.dump -T 'Fio Benchmark' -p 'fio some_job_file'
62 Please email chris.mason@fusionio.com with any questions