1perf-timechart(1) 2================= 3 4NAME 5---- 6perf-timechart - Tool to visualize total system behavior during a workload 7 8SYNOPSIS 9-------- 10[verse] 11'perf timechart' [<timechart options>] {record} [<record options>] 12 13DESCRIPTION 14----------- 15There are two variants of perf timechart: 16 17 'perf timechart record <command>' to record the system level events 18 of an arbitrary workload. By default timechart records only scheduler 19 and CPU events (task switches, running times, CPU power states, etc), 20 but it's possible to record IO (disk, network) activity using -I argument. 21 22 'perf timechart' to turn a trace into a Scalable Vector Graphics file, 23 that can be viewed with popular SVG viewers such as 'Inkscape'. Depending 24 on the events in the perf.data file, timechart will contain scheduler/cpu 25 events or IO events. 26 27 In IO mode, every bar has two charts: upper and lower. 28 Upper bar shows incoming events (disk reads, ingress network packets). 29 Lower bar shows outgoing events (disk writes, egress network packets). 30 There are also poll bars which show how much time application spent 31 in poll/epoll/select syscalls. 32 33TIMECHART OPTIONS 34----------------- 35-o:: 36--output=:: 37 Select the output file (default: output.svg) 38-i:: 39--input=:: 40 Select the input file (default: perf.data unless stdin is a fifo) 41-w:: 42--width=:: 43 Select the width of the SVG file (default: 1000) 44-P:: 45--power-only:: 46 Only output the CPU power section of the diagram 47-T:: 48--tasks-only:: 49 Don't output processor state transitions 50-p:: 51--process:: 52 Select the processes to display, by name or PID 53 54--symfs=<directory>:: 55 Look for files with symbols relative to this directory. 56-n:: 57--proc-num:: 58 Print task info for at least given number of tasks. 59-t:: 60--topology:: 61 Sort CPUs according to topology. 62--highlight=<duration_nsecs|task_name>:: 63 Highlight tasks (using different color) that run more than given 64 duration or tasks with given name. If number is given it's interpreted 65 as number of nanoseconds. If non-numeric string is given it's 66 interpreted as task name. 67 68RECORD OPTIONS 69-------------- 70-P:: 71--power-only:: 72 Record only power-related events 73-T:: 74--tasks-only:: 75 Record only tasks-related events 76-I:: 77--io-only:: 78 Record only io-related events 79-g:: 80--callchain:: 81 Do call-graph (stack chain/backtrace) recording 82 83EXAMPLES 84-------- 85 86$ perf timechart record git pull 87 88 [ perf record: Woken up 13 times to write data ] 89 [ perf record: Captured and wrote 4.253 MB perf.data (~185801 samples) ] 90 91$ perf timechart 92 93 Written 10.2 seconds of trace to output.svg. 94 95Record system-wide timechart: 96 97 $ perf timechart record 98 99 then generate timechart and highlight 'gcc' tasks: 100 101 $ perf timechart --highlight gcc 102 103Record system-wide IO events: 104 105 $ perf timechart record -I 106 107 then generate timechart: 108 109 $ perf timechart 110 111SEE ALSO 112-------- 113linkperf:perf-record[1] 114