Hardware-Based Performance Monitoring with Perf | System Analysis and Tuning Guide

openSUSE Leap Documentation › System Analysis and Tuning Guide › Kernel Monitoring › Hardware-Based Performance Monitoring with Perf

Applies to openSUSE Leap 42.1

6 Hardware-Based Performance Monitoring with Perf

Abstract#

Perf is an interface to access the performance monitoring unit (PMU) of a processor and to record and display software events such as page faults. It supports system-wide, per-thread, and KVM virtualization guest monitoring.

6.1 Hardware-Based Monitoring
6.2 Sampling and Counting
6.3 Installing Perf
6.4 Perf Subcommands
6.5 Counting Particular Types of Event
6.6 Recording Events Specific to Particular Commands
6.7 For More Information

You can store resulting information in a report. This report contains information about, for example, instruction pointers or what code a thread was executing.

Perf consists of two parts:

Code integrated into the Linux kernel that is responsible for instructing the hardware.
The perf userspace utility that allows you to use the kernel code and helps you analyze gathered data.

6.1 Hardware-Based Monitoring #

Performance monitoring means collecting information related to how an application or system performs. This information can be obtained either through software-based means or from the CPU or chipset. Perf integrates both of these methods.

Many modern processors contain a performance monitoring unit (PMU). The design and functionality of a PMU is CPU-specific. For example, the number of registers, counters and features supported will vary by CPU implementation.

Each PMU model consists of a set of registers: the performance monitor configuration (PMC) and the performance monitor data (PMD). Both can be read, but only PMCs are writable. These registers store configuration information and data.

6.2 Sampling and Counting #

Perf supports several profiling modes:

Counting. Count the number of occurrences of an event.
Event-Based Sampling. A less exact way of counting: A sample is recorded whenever a certain threshold number of events has occurred.
Time-Based Sampling. A less exact way of counting: A sample is recorded in a defined frequency.
Instruction-Based Sampling (AMD64 only). The processor follows instructions appearing in a given interval and samples which events they produce. This allows following up on individual instructions and seeing which of them is critical to performance.
Instruction-Based Sampling (AMD64 only). The processor follows instructions appearing in a given interval and samples which events they produce. This allows following up on individual instructions and seeing which of them is critical to performance.

6.3 Installing Perf #

The Perf kernel code is already included with the default kernel. To be able to use the userspace utility, install the package perf.

6.4 Perf Subcommands #

To gather the required information, the perf tool has several subcommands. This section gives an overview of the most often used commands.

To see help in the form of a man page for any of the subcommands, use either perf helpSUBCOMMAND or man perf-SUBCOMMAND.

perf stat

Start a program and create a statistical overview that is displayed after the program quits. perf stat is used to count events.

perf record

Start a program and create a report with performance counter information. The report is stored as perf.data in the current directory. perf record is used to sample events.

perf report

Display a report that was previously created with perf record.

perf annotate

Display a report file and an annotated version of the executed code. If debug symbols are installed, you will also see the source code displayed.

perf list

List event types that Perf can report with the current kernel and with your CPU. You can filter event types by category—for example, to see hardware events only, use perf list hw.

The man page for perf_event_open has short descriptions for the most important events. For example, to find a description of the event branch-misses, search for BRANCH_MISSES (note the spelling differences):

tux > man perf_event_open | grep -A5 BRANCH_MISSES

Sometimes, events may be ambiguous. Note that the lowercase hardware event names are not the name of raw hardware events but instead the name of aliases created by Perf. These aliases map to differently named but similarly defined hardware events on each supported processor.

For example, the cpu-cycles event is mapped to the hardware event UNHALTED_CORE_CYCLES on Intel processors. On AMD processors, however, it is mapped to hardware event CPU_CLK_UNHALTED.

Perf also allows measuring raw events specific to your hardware. To look up their descriptions, see the Architecture Software Developer's Manual of your CPU vendor. The relevant documents for AMD64/Intel 64 processors are linked to in Section 6.7, “For More Information”.

perf top

Display system activity as it happens.

perf trace

This command behaves similarly to strace. With this subcommand, you can see which system calls are executed by a particular thread or process and which signals it receives.

6.5 Counting Particular Types of Event #

To count the number of occurrences of an event, such as those displayed by perf list, use:

root # perf stat -e EVENT -a

To count multiple types of events at once, list them separated by commas. For example, to count cpu-cycles and instructions, use:

root # perf stat -e cpu-cycles,instructions -a

To stop the session, press Ctrl–C.

You can also count the number of occurrences of an event within a particular time:

root # perf stat -e EVENT -a -- sleep TIME

Replace TIME by a value in seconds.

6.6 Recording Events Specific to Particular Commands #

There are various ways to sample events specific to a particular command:

To create a report for a newly invoked command, use:
```
root # perf record COMMAND
```
Then, use the started process normally. When you quit the process, the Perf session will also stop.
To create a report for the entire system while a newly invoked command is running, use:
```
root # perf record -a COMMAND
```
Then, use the started process normally. When you quit the process, the Perf session will also stop.
To create a report for an already running process, use:
```
root # perf record -p PID
```
Replace PID with a process ID. To stop the session, press Ctrl–C.

Afterwards, you can view the gathered data (perf.data) using:

tux > perf report

This will open a pseudo-graphical interface. To receive help, press H. To quit, press Q.

If you prefer a graphical interface, try the GTK+ interface of Perf:

tux > perf report --gtk

However, note that the GTK+ interface is very limited in functionality.

6.7 For More Information #

This chapter only provides a short overview. Refer to the following links for more information:

https://perf.wiki.kernel.org/index.php/Main_Page: The project home page. It also features a tutorial on using perf.
http://www.brendangregg.com/perf.html: Unofficial page with many one-line examples of how to use perf.
http://web.eece.maine.edu/~vweaver/projects/perf_events/: Unofficial page with several resources, mostly relating to the Linux kernel code of Perf and its API. This page includes, for example, a CPU compatibility table and a programming guide.
https://www-ssl.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-software-developer-vol-3b-part-2-manual.pdf: The Intel Architectures Software Developer's Manual, Volume 3B.
https://support.amd.com/TechDocs/24593.pdf: The AMD Architecture Programmer's Manual, Volume 2.
Chapter 7, OProfile—System-Wide Profiler: Consult this chapter for other performance optimizations.

Print this page