There are two variants of perf timechart:
'perf timechart record <command>' to record the system level events
of an arbitrary workload. By default timechart records only scheduler
and CPU events (task switches, running times, CPU power states, etc),
but it's possible to record IO (disk, network) activity using -I argument.
'perf timechart' to turn a trace into a Scalable Vector Graphics file,
that can be viewed with popular SVG viewers such as 'Inkscape'. Depending
on the events in the perf.data file, timechart will contain scheduler/cpu
events or IO events.
In IO mode, every bar has two charts: upper and lower.
Upper bar shows incoming events (disk reads, ingress network packets).
Lower bar shows outgoing events (disk writes, egress network packets).
There are also poll bars which show how much time application spent
in poll/epoll/select syscalls.
Select the output file (default: output.svg)
Select the input file (default: perf.data unless stdin is a fifo)
Select the width of the SVG file (default: 1000)
Only output the CPU power section of the diagram
Don’t output processor state transitions
Select the processes to display, by name or PID
Look for files with symbols relative to this directory.
Print task info for at least given number of tasks.
Sort CPUs according to topology.
Highlight tasks (using different color) that run more than given
duration or tasks with given name. If number is given it’s
interpreted as number of nanoseconds. If non-numeric string is
given it’s interpreted as task name.
Don’t draw EAGAIN IO events.
Draw small events as if they lasted min-time. Useful when you
need to see very small and fast IO. It’s possible to specify ms
or us suffix to specify time in milliseconds or microseconds.
Default value is 1ms.
Merge events that are merge-dist nanoseconds apart. Reduces
number of figures on the SVG and makes it more render-friendly.
It’s possible to specify ms or us suffix to specify time in
milliseconds or microseconds. Default value is 1us.
Record only power-related events
Record only tasks-related events
Record only io-related events
Do call-graph (stack chain/backtrace) recording
$ perf timechart record git pull
[ perf record: Woken up 13 times to write data ]
[ perf record: Captured and wrote 4.253 MB perf.data (~185801 samples) ]
$ perf timechart
Written 10.2 seconds of trace to output.svg.
Record system-wide timechart:
$ perf timechart record
then generate timechart and highlight 'gcc' tasks:
$ perf timechart --highlight gcc
Record system-wide IO events:
$ perf timechart record -I
then generate timechart:
$ perf timechart
This page is part of the perf (Performance analysis tools for Linux
(in Linux source tree)) project. Information about the project can
be found at ⟨https://perf.wiki.kernel.org/index.php/Main_Page⟩. If
you have a bug report for this manual page, send it to
firstname.lastname@example.org. This page was obtained from the
project's upstream Git repository
2017-03-13. If you discover any rendering problems in this HTML ver‐
sion of the page, or you believe there is a better or more up-to-date
source for the page, or you have corrections or improvements to the
information in this COLOPHON (which is not part of the original man‐
ual page), send a mail to email@example.com
perf 02/18/2017 PERF-TIMECHART(1)