btt

Analyze block trace data

$ btt -i [sda.blktrace.0]

$ btt -i [device.blktrace.0] -o [analysis]

$ btt -i [trace.blktrace.0] -q [q2c_output]

$ btt -i [trace.blktrace.0] -d [d2c_output]

$ blkparse -i [sda] -d [merged.bin] && btt -i [merged.bin]

$ btt -i [trace.blktrace.0] -v

btt [options] -i tracefile_

btt (Block Trace Timeline) analyzes block layer trace data generated by blktrace. It produces statistical reports showing I/O latency distributions, throughput, and timing breakdowns across the block I/O stack.
The analysis breaks down request processing into stages: Q (queued), G (get request), I (inserted), M (merged), D (dispatched), C (completed). btt reports latencies between these stages to identify bottlenecks.
Output includes overall statistics, per-device breakdowns, and optional detailed timing files for each stage transition. This data is valuable for understanding storage performance characteristics and diagnosing latency issues.

-i file

Input trace file (from blkparse -d).

Output file prefix.

Write Q2C latency data.

Write D2C latency data.

Write per-IO latency data.

Write D2D seek distance data.

Write block number data.

Verbose output.

Version information.

Include all accounting.

Only display device mapping info.

Requires binary trace data from blkparse -d, not raw blktrace files. Large traces produce large analysis output. Timestamps must be synchronized for meaningful analysis. Output files can be plotted with gnuplot for visualization.

btt was developed alongside blktrace by Alan D. Brunelle as part of the Linux block layer tracing infrastructure, included in the blktrace package since its introduction in Linux kernel 2.6.17 (2006). It provides the analytical companion to blktrace's data collection capabilities, enabling detailed performance analysis of the block I/O subsystem.

blktrace(8), blkparse(1), iowatcher(1), iostat(1)