blob: bd0e4417f2be63f892a870ec5ad60ae0fd5d9994 [file] [log] [blame]
Ingo Molnar1d8c8b22009-04-20 15:52:29 +02001perf-stat(1)
Ingo Molnar6e6b7542008-04-15 22:39:31 +02002============
Ingo Molnar1d8c8b22009-04-20 15:52:29 +02003
4NAME
5----
6perf-stat - Run a command and gather performance counter statistics
7
8SYNOPSIS
9--------
10[verse]
Shawn Bohrer8c207692010-11-30 19:57:19 -060011'perf stat' [-e <EVENT> | --event=EVENT] [-a] <command>
12'perf stat' [-e <EVENT> | --event=EVENT] [-a] -- <command> [<options>]
Jiri Olsa4979d0c2015-11-05 15:40:46 +010013'perf stat' [-e <EVENT> | --event=EVENT] [-a] record [-o file] -- <command> [<options>]
Jiri Olsaba6039b62015-11-05 15:40:55 +010014'perf stat' report [-i file]
Ingo Molnar1d8c8b22009-04-20 15:52:29 +020015
16DESCRIPTION
17-----------
18This command runs a command and gathers performance counter statistics
19from it.
20
21
22OPTIONS
23-------
24<command>...::
25 Any command you can specify in a shell.
26
Jiri Olsa4979d0c2015-11-05 15:40:46 +010027record::
28 See STAT RECORD.
Ingo Molnar20c84e92009-06-04 16:33:00 +020029
Jiri Olsaba6039b62015-11-05 15:40:55 +010030report::
31 See STAT REPORT.
32
Ingo Molnar1d8c8b22009-04-20 15:52:29 +020033-e::
34--event=::
Cody P Schaferf9ab9c12015-01-07 17:13:53 -080035 Select the PMU event. Selection can be:
36
37 - a symbolic event name (use 'perf list' to list all events)
38
39 - a raw PMU event (eventsel+umask) in the form of rNNN where NNN is a
40 hexadecimal event descriptor.
41
42 - a symbolically formed event like 'pmu/param1=0x3,param2/' where
43 param1 and param2 are defined as formats for the PMU in
44 /sys/bus/event_sources/devices/<pmu>/format/*
45
46 - a symbolically formed event like 'pmu/config=M,config1=N,config2=K/'
47 where M, N, K are numbers (in decimal, hex, octal format).
48 Acceptable values for each of 'config', 'config1' and 'config2'
49 parameters are defined by corresponding entries in
50 /sys/bus/event_sources/devices/<pmu>/format/*
Ingo Molnar1d8c8b22009-04-20 15:52:29 +020051
Ingo Molnar20c84e92009-06-04 16:33:00 +020052-i::
Stephane Eranian2e6cdf92010-05-12 10:40:01 +020053--no-inherit::
54 child tasks do not inherit counters
Ingo Molnar20c84e92009-06-04 16:33:00 +020055-p::
56--pid=<pid>::
David Ahernb52956c2012-02-08 09:32:52 -070057 stat events on existing process id (comma separated list)
Shawn Bohrer8c207692010-11-30 19:57:19 -060058
59-t::
60--tid=<tid>::
David Ahernb52956c2012-02-08 09:32:52 -070061 stat events on existing thread id (comma separated list)
Shawn Bohrer8c207692010-11-30 19:57:19 -060062
Ingo Molnar20c84e92009-06-04 16:33:00 +020063
Ingo Molnar1d8c8b22009-04-20 15:52:29 +020064-a::
Shawn Bohrer8c207692010-11-30 19:57:19 -060065--all-cpus::
Jiri Olsa0d79f8b2017-02-17 18:00:34 +010066 system-wide collection from all CPUs (default if no target is specified)
Ingo Molnar1d8c8b22009-04-20 15:52:29 +020067
Brice Goglinb26bc5a2009-08-07 10:18:39 +020068-c::
Shawn Bohrer8c207692010-11-30 19:57:19 -060069--scale::
70 scale/normalize counter values
71
Borislav Petkovf594bae2016-03-07 16:44:44 -030072-d::
73--detailed::
74 print more detailed statistics, can be specified up to 3 times
75
76 -d: detailed events, L1 and LLC data cache
77 -d -d: more detailed events, dTLB and iTLB events
78 -d -d -d: very detailed events, adding prefetch events
79
Shawn Bohrer8c207692010-11-30 19:57:19 -060080-r::
81--repeat=<n>::
Frederik Deweerdta7e191c2013-03-01 13:02:27 -050082 repeat command and print average + stddev (max: 100). 0 means forever.
Ingo Molnar1d8c8b22009-04-20 15:52:29 +020083
Stephane Eranian5af52b52010-05-18 15:00:01 +020084-B::
Shawn Bohrer8c207692010-11-30 19:57:19 -060085--big-num::
Stephane Eranian5af52b52010-05-18 15:00:01 +020086 print large numbers with thousands' separators according to locale
87
Stephane Eranianc45c6ea2010-05-28 12:00:01 +020088-C::
89--cpu=::
Shawn Bohrer8c207692010-11-30 19:57:19 -060090Count only on the list of CPUs provided. Multiple CPUs can be provided as a
91comma-separated list with no space: 0,1. Ranges of CPUs are specified with -: 0-2.
Stephane Eranianc45c6ea2010-05-28 12:00:01 +020092In per-thread mode, this option is ignored. The -a option is still necessary
93to activate system-wide monitoring. Default is to count on all CPUs.
94
Stephane Eranianf5b4a9c32010-11-16 11:05:01 +020095-A::
96--no-aggr::
Ravi Bangoriaefc9c052017-03-20 18:07:18 +053097Do not aggregate counts across all monitored CPUs.
Stephane Eranianf5b4a9c32010-11-16 11:05:01 +020098
Shawn Bohrer8c207692010-11-30 19:57:19 -060099-n::
100--null::
101 null run - don't start any counters
102
103-v::
104--verbose::
105 be more verbose (show counter open errors, etc)
106
Stephane Eraniand7470b62010-12-01 18:49:05 +0200107-x SEP::
108--field-separator SEP::
109print counts using a CSV-style output to make it easy to import directly into
110spreadsheets. Columns are separated by the string specified in SEP.
111
Stephane Eranian023695d2011-02-14 11:20:01 +0200112-G name::
113--cgroup name::
114monitor only in the container (cgroup) called "name". This option is available only
115in per-cpu mode. The cgroup filesystem must be mounted. All threads belonging to
116container "name" are monitored when they run on the monitored CPUs. Multiple cgroups
117can be provided. Each cgroup is applied to the corresponding event, i.e., first cgroup
118to first event, second cgroup to second event and so on. It is possible to provide
119an empty cgroup (monitor all the time) using, e.g., -G foo,,bar. Cgroups must have
120corresponding events, i.e., they always refer to events defined earlier on the command
121line.
122
Stephane Eranian4aa90152011-08-15 22:22:33 +0200123-o file::
Jim Cromie56f3bae2011-09-07 17:14:00 -0600124--output file::
Stephane Eranian4aa90152011-08-15 22:22:33 +0200125Print the output into the designated file.
126
127--append::
128Append to the output file designated with the -o option. Ignored if -o is not specified.
129
Jim Cromie56f3bae2011-09-07 17:14:00 -0600130--log-fd::
131
132Log output to fd, instead of stderr. Complementary to --output, and mutually exclusive
133with it. --append may be used here. Examples:
134 3>results perf stat --log-fd 3 -- $cmd
135 3>>results perf stat --log-fd 3 --append -- $cmd
136
Peter Zijlstra1f16c572012-10-23 13:40:14 +0200137--pre::
138--post::
139 Pre and post measurement hooks, e.g.:
140
141perf stat --repeat 10 --null --sync --pre 'make -s O=defconfig-build/clean' -- make -s -j64 O=defconfig-build/ bzImage
Jim Cromie56f3bae2011-09-07 17:14:00 -0600142
Stephane Eranian13370a92013-01-29 12:47:44 +0100143-I msecs::
144--interval-print msecs::
Kan Liang19afd102015-10-02 05:04:34 -0400145Print count deltas every N milliseconds (minimum: 10ms)
146The overhead percentage could be high in some cases, for instance with small, sub 100ms intervals. Use with caution.
147 example: 'perf stat -I 1000 -e cycles -a sleep 5'
Jim Cromie56f3bae2011-09-07 17:14:00 -0600148
Andi Kleen54b50912016-03-03 15:57:36 -0800149--metric-only::
150Only print computed metrics. Print them in a single line.
Andi Kleen206cab62016-03-03 15:57:37 -0800151Don't show any raw values. Not supported with --per-thread.
Andi Kleen54b50912016-03-03 15:57:36 -0800152
Stephane Eraniand4304952013-02-14 13:57:28 +0100153--per-socket::
Stephane Eraniand7e7a452013-02-06 15:46:02 +0100154Aggregate counts per processor socket for system-wide mode measurements. This
155is a useful mode to detect imbalance between sockets. To enable this mode,
Stephane Eraniand4304952013-02-14 13:57:28 +0100156use --per-socket in addition to -a. (system-wide). The output includes the
Stephane Eraniand7e7a452013-02-06 15:46:02 +0100157socket number and the number of online processors on that socket. This is
158useful to gauge the amount of aggregation.
159
Stephane Eranian12c08a92013-02-14 13:57:29 +0100160--per-core::
161Aggregate counts per physical processor for system-wide mode measurements. This
162is a useful mode to detect imbalance between physical cores. To enable this mode,
163use --per-core in addition to -a. (system-wide). The output includes the
164core number and the number of online logical processors on that physical processor.
165
Jiri Olsa32b8af82015-06-26 11:29:27 +0200166--per-thread::
167Aggregate counts per monitored threads, when monitoring threads (-t option)
168or processes (-p option).
169
Andi Kleen41191682013-08-02 17:41:11 -0700170-D msecs::
Andi Kleen8f3dd2b2014-01-07 14:14:06 -0800171--delay msecs::
Andi Kleen41191682013-08-02 17:41:11 -0700172After starting the program, wait msecs before measuring. This is useful to
173filter out the startup phase of the program, which is often very different.
174
Andi Kleen4cabc3d2013-08-21 16:47:26 -0700175-T::
176--transaction::
177
178Print statistics of transactional execution if supported.
179
Jiri Olsa4979d0c2015-11-05 15:40:46 +0100180STAT RECORD
181-----------
182Stores stat data into perf data file.
183
184-o file::
185--output file::
186Output file name.
187
Jiri Olsaba6039b62015-11-05 15:40:55 +0100188STAT REPORT
189-----------
190Reads and reports stat data from perf data file.
191
192-i file::
193--input file::
194Input file name.
195
Jiri Olsa89af4e02015-11-05 15:41:02 +0100196--per-socket::
197Aggregate counts per processor socket for system-wide mode measurements.
198
199--per-core::
200Aggregate counts per physical processor for system-wide mode measurements.
201
202-A::
203--no-aggr::
204Do not aggregate counts across all monitored CPUs.
205
Andi Kleen44b1e602016-05-30 12:49:42 -0300206--topdown::
207Print top down level 1 metrics if supported by the CPU. This allows to
208determine bottle necks in the CPU pipeline for CPU bound workloads,
209by breaking the cycles consumed down into frontend bound, backend bound,
210bad speculation and retiring.
211
212Frontend bound means that the CPU cannot fetch and decode instructions fast
213enough. Backend bound means that computation or memory access is the bottle
214neck. Bad Speculation means that the CPU wasted cycles due to branch
215mispredictions and similar issues. Retiring means that the CPU computed without
216an apparently bottleneck. The bottleneck is only the real bottleneck
217if the workload is actually bound by the CPU and not by something else.
218
219For best results it is usually a good idea to use it with interval
220mode like -I 1000, as the bottleneck of workloads can change often.
221
222The top down metrics are collected per core instead of per
223CPU thread. Per core mode is automatically enabled
224and -a (global monitoring) is needed, requiring root rights or
225perf.perf_event_paranoid=-1.
226
227Topdown uses the full Performance Monitoring Unit, and needs
228disabling of the NMI watchdog (as root):
229echo 0 > /proc/sys/kernel/nmi_watchdog
230for best results. Otherwise the bottlenecks may be inconsistent
231on workload with changing phases.
232
233This enables --metric-only, unless overriden with --no-metric-only.
234
235To interpret the results it is usually needed to know on which
236CPUs the workload runs on. If needed the CPUs can be forced using
237taskset.
Jiri Olsa4979d0c2015-11-05 15:40:46 +0100238
Andi Kleen430daf22017-03-20 13:17:00 -0700239--no-merge::
240Do not merge results from same PMUs.
241
Ingo Molnar1d8c8b22009-04-20 15:52:29 +0200242EXAMPLES
243--------
244
Ingo Molnar20c84e92009-06-04 16:33:00 +0200245$ perf stat -- make -j
Ingo Molnar1d8c8b22009-04-20 15:52:29 +0200246
Ingo Molnar20c84e92009-06-04 16:33:00 +0200247 Performance counter stats for 'make -j':
Ingo Molnar1d8c8b22009-04-20 15:52:29 +0200248
Ingo Molnar20c84e92009-06-04 16:33:00 +0200249 8117.370256 task clock ticks # 11.281 CPU utilization factor
250 678 context switches # 0.000 M/sec
251 133 CPU migrations # 0.000 M/sec
252 235724 pagefaults # 0.029 M/sec
253 24821162526 CPU cycles # 3057.784 M/sec
254 18687303457 instructions # 2302.138 M/sec
255 172158895 cache references # 21.209 M/sec
256 27075259 cache misses # 3.335 M/sec
Ingo Molnar1d8c8b22009-04-20 15:52:29 +0200257
Ingo Molnar20c84e92009-06-04 16:33:00 +0200258 Wall-clock time elapsed: 719.554352 msecs
Ingo Molnar1d8c8b22009-04-20 15:52:29 +0200259
Andi Kleen6b45f7b2016-03-03 15:57:35 -0800260CSV FORMAT
261----------
262
263With -x, perf stat is able to output a not-quite-CSV format output
264Commas in the output are not put into "". To make it easy to parse
265it is recommended to use a different character like -x \;
266
267The fields are in this order:
268
269 - optional usec time stamp in fractions of second (with -I xxx)
270 - optional CPU, core, or socket identifier
271 - optional number of logical CPUs aggregated
272 - counter value
273 - unit of the counter value or empty
274 - event name
275 - run time of counter
276 - percentage of measurement time the counter was running
277 - optional variance if multiple values are collected with -r
278 - optional metric value
279 - optional unit of metric
280
281Additional metrics may be printed with all earlier fields being empty.
282
Ingo Molnar1d8c8b22009-04-20 15:52:29 +0200283SEE ALSO
284--------
Thomas Gleixner386b05e2009-06-06 14:56:33 +0200285linkperf:perf-top[1], linkperf:perf-list[1]