Difference between revisions of "Runtime profiling"

From HPC Wiki
Jump to navigation Jump to search
Line 8: Line 8:
 
The first step is to compile and link the program with profiling enabled. For most compilers this is achieved by setting the ```-pg``` flag. For Intel compilers it is important to set the optimization flag afterward as the default optimization level is set to ```-O0``` when enabling profiling.
 
The first step is to compile and link the program with profiling enabled. For most compilers this is achieved by setting the ```-pg``` flag. For Intel compilers it is important to set the optimization flag afterward as the default optimization level is set to ```-O0``` when enabling profiling.
  
Example for Intel tool chain:
+
Example for build options with Intel tool chain:
  
 
<syntaxhighlight lang="sh">
 
<syntaxhighlight lang="sh">
Line 14: Line 14:
 
icc -pg -O3 -c  myfile2.c
 
icc -pg -O3 -c  myfile2.c
 
icc -o a.out -pg  myfile1.o myfile2.o
 
icc -o a.out -pg  myfile1.o myfile2.o
 +
</syntaxhighlight>
 +
 +
The generated application is executed and generates a ```gmon.out``` file containing the profiling output.
 +
To analyse the profile the tool ```gprof``` is used with the executable as argument:
 +
 +
<syntaxhighlight lang="sh">
 +
gprof ./miniMD
 +
</syntaxhighlight>
 +
 +
Refer to the gprof man page for additional command line options. The result will be printed on stdout. It is recommended to either redirect the output to a file or use a pipe to the less pager command.
 +
 +
<syntaxhighlight lang="sh">
 +
gprof ./miniMD | less
 +
</syntaxhighlight>
 +
 +
The default output consists of three parts: A flat profile, the call graph, and  an alphabetical index of routines. For most purposes the flat profile is what you are looking for.
 +
 +
Example output of the flat profile for the Mantevo miniMD proxy app:
 +
 +
<syntaxhighlight lang="sh">
 +
Each sample counts as 0.01 seconds.
 +
  %  cumulative  self              self    total
 +
time  seconds  seconds    calls  s/call  s/call  name
 +
66.86    26.14    26.14      502    0.05    0.05  ForceLJ::compute(Atom&, Neighbor&, Comm&, int)
 +
30.77    38.17    12.03      26    0.46    0.46  Neighbor::build(Atom&)
 +
  1.43    38.73    0.56        1    0.56    38.46  Integrate::run(Atom&, Force*, Neighbor&, Comm&, Thermo&, Timer&)
 +
  0.36    38.87    0.14    2850    0.00    0.00  Atom::pack_comm(int, int*, double*, int*)
 +
  0.15    38.93    0.06    2850    0.00    0.00  Atom::unpack_comm(int, int, double*)
 +
  0.13    38.98    0.05      26    0.00    0.00  Atom::pbc()
 +
  0.10    39.02    0.04                            __intel_ssse3_rep_memcpy
 +
  0.08    39.05    0.03      25    0.00    0.00  Atom::sort(Neighbor&)
 +
  0.08    39.08    0.03        1    0.03    0.03  create_atoms(Atom&, int, int, int, double)
 +
  0.05    39.10    0.02      26    0.00    0.00  Comm::borders(Atom&)
 +
  0.00    39.10    0.00  1221559    0.00    0.00  Atom::pack_border(int, double*, int*)
 +
  0.00    39.10    0.00  1221559    0.00    0.00  Atom::unpack_border(int, double*)
 +
  0.00    39.10    0.00  131072    0.00    0.00  Atom::addatom(double, double, double, double, double, double)
 +
  0.00    39.10    0.00    1025    0.00    0.00  Timer::stamp(int)
 +
  0.00    39.10    0.00      502    0.00    0.00  Thermo::compute(int, Atom&, Neighbor&, Force*, Timer&, Comm&)
 +
  0.00    39.10    0.00      500    0.00    0.00  Timer::stamp()
 +
  0.00    39.10    0.00      475    0.00    0.00  Comm::communicate(Atom&)
 +
  0.00    39.10    0.00      26    0.00    0.00  Comm::exchange(Atom&)
 +
  0.00    39.10    0.00      25    0.00    0.00  Timer::stamp_extra_stop(int)
 +
  0.00    39.10    0.00      25    0.00    0.00  Timer::stamp_extra_start()
 +
  0.00    39.10    0.00      25    0.00    0.00  Neighbor::binatoms(Atom&, int)
 +
  0.00    39.10    0.00        7    0.00    0.00  Timer::barrier_stop(int)
 +
  0.00    39.10    0.00        1    0.00    0.00  create_box(Atom&, int, int, int, double)
 +
  0.00    39.10    0.00        1    0.00    0.00  create_velocity(double, Atom&, Thermo&)
 
</syntaxhighlight>
 
</syntaxhighlight>
  
 
== How to use perf ==
 
== How to use perf ==

Revision as of 14:50, 2 April 2019

Introduction

The initial task in any performance analysis is to figure out in which parts of the code the runtime is spent. One wants to focus for optimisation on those regions of the code to achieve an overall speedup of the code. The tool helping to get an overview of where the time is spent is called a runtime profiler. There exist two flavours: Instrumentation based and sampling based profilers. Instrumentation based profilers insert function calls to measure the time at points in the program. Additional tasks may be performed as e.g. determining the function call stack. While it is possible to insert instrumentation calls on the binary level the common way is that the compiler adds instrumentation functions. The standard tool in this area is gprof and almost any compiler supports to instrument the code for gprof. Statistical sampling based profiling on the other hand are based on probing of the programs call stack triggered by operating system interrupts at regular intervals. A widespread tool for sampling based profiling is the perf tool which builds on the builtin profiling infrastructure in recent Linux kernels. Both approaches have advantages and disadvantages: Instrumentation produces more accurate results but introduces more overhead and sampling has less overhead but produce less accurate results. Special care is necessary for runtime profiling of parallel (OpenMP or MPI) applications.

How to use gprof

The first step is to compile and link the program with profiling enabled. For most compilers this is achieved by setting the ```-pg``` flag. For Intel compilers it is important to set the optimization flag afterward as the default optimization level is set to ```-O0``` when enabling profiling.

Example for build options with Intel tool chain:

icc -pg -O3 -c  myfile1.c
icc -pg -O3 -c  myfile2.c
icc -o a.out -pg  myfile1.o myfile2.o

The generated application is executed and generates a ```gmon.out``` file containing the profiling output. To analyse the profile the tool ```gprof``` is used with the executable as argument:

gprof ./miniMD

Refer to the gprof man page for additional command line options. The result will be printed on stdout. It is recommended to either redirect the output to a file or use a pipe to the less pager command.

gprof ./miniMD | less

The default output consists of three parts: A flat profile, the call graph, and an alphabetical index of routines. For most purposes the flat profile is what you are looking for.

Example output of the flat profile for the Mantevo miniMD proxy app:

Each sample counts as 0.01 seconds.
  %   cumulative   self              self     total
 time   seconds   seconds    calls   s/call   s/call  name
 66.86     26.14    26.14      502     0.05     0.05  ForceLJ::compute(Atom&, Neighbor&, Comm&, int)
 30.77     38.17    12.03       26     0.46     0.46  Neighbor::build(Atom&)
  1.43     38.73     0.56        1     0.56    38.46  Integrate::run(Atom&, Force*, Neighbor&, Comm&, Thermo&, Timer&)
  0.36     38.87     0.14     2850     0.00     0.00  Atom::pack_comm(int, int*, double*, int*)
  0.15     38.93     0.06     2850     0.00     0.00  Atom::unpack_comm(int, int, double*)
  0.13     38.98     0.05       26     0.00     0.00  Atom::pbc()
  0.10     39.02     0.04                             __intel_ssse3_rep_memcpy
  0.08     39.05     0.03       25     0.00     0.00  Atom::sort(Neighbor&)
  0.08     39.08     0.03        1     0.03     0.03  create_atoms(Atom&, int, int, int, double)
  0.05     39.10     0.02       26     0.00     0.00  Comm::borders(Atom&)
  0.00     39.10     0.00  1221559     0.00     0.00  Atom::pack_border(int, double*, int*)
  0.00     39.10     0.00  1221559     0.00     0.00  Atom::unpack_border(int, double*)
  0.00     39.10     0.00   131072     0.00     0.00  Atom::addatom(double, double, double, double, double, double)
  0.00     39.10     0.00     1025     0.00     0.00  Timer::stamp(int)
  0.00     39.10     0.00      502     0.00     0.00  Thermo::compute(int, Atom&, Neighbor&, Force*, Timer&, Comm&)
  0.00     39.10     0.00      500     0.00     0.00  Timer::stamp()
  0.00     39.10     0.00      475     0.00     0.00  Comm::communicate(Atom&)
  0.00     39.10     0.00       26     0.00     0.00  Comm::exchange(Atom&)
  0.00     39.10     0.00       25     0.00     0.00  Timer::stamp_extra_stop(int)
  0.00     39.10     0.00       25     0.00     0.00  Timer::stamp_extra_start()
  0.00     39.10     0.00       25     0.00     0.00  Neighbor::binatoms(Atom&, int)
  0.00     39.10     0.00        7     0.00     0.00  Timer::barrier_stop(int)
  0.00     39.10     0.00        1     0.00     0.00  create_box(Atom&, int, int, int, double)
  0.00     39.10     0.00        1     0.00     0.00  create_velocity(double, Atom&, Thermo&)

How to use perf