Integrated Performance Monitoring for HPC
IPM uses the common GNU autotools build system for compilation. As such, a
typical install of IPM from this repository must begin by generating the
autoconf configure script via our provided bootstrap.sh script:
./bootstrap.sh
Once this is done, you should be able to run
./configure
make
make install
As usual, you will likely want to examine key options available for the
configure script, which can be viewed by running ./configure --help. For
example, you can enable support for hardware performance counter collection via
PAPI by specifying the PAPI installation path using the --with-papi=<path>
option. You may also need to specify your MPI compiler wrappers via the MPICC
and MPIFC variables - see ./configure --help for details.
Once you have built and installed IPM, using it to profile your application
should be fairly straightforward. Suppose that $PREFIX is the installation
prefix you used when installing IPM. In this case, you can enable profiling by
appending
-L$PREFIX -lipm
to your link line (making sure it is the last argument). If you are linking an
application that uses the Fortran bindings to MPI, then you will also need to
add -lipmf, making sure that it comes before -lipm:
-L$PREFIX -lipmf -lipm
As usual, if you are using dynamic linking and $PREFIX/lib has not been added
to your $LD_LIBRARY_PATH, then you will likely also want to pass the former
to the linker as an -rpath.
Note: The master branch of IPM is in general usable, but should be
considered development software. We strongly recommend that for production use
you build a tagged release of IPM. The most recent release is 2.0.4.
Suppose that you are building a pure C MPI code contained in a single source
file that you would like to profile with IPM, and that mpicc is the MPI C
compiler wrapper for your system. In this case, you could simply run:
mpicc my_code.c -o my_code.x -L$PREFIX/lib -lipm
to produce an IPM instrumented executable.
Now suppose that you are building a mixed C and Fortran MPI code that you would
like to profile with IPM, and that mpicc and mpifort are the MPI C and
Fortran compiler wrappers for your system. In this case, you could use:
mpicc -c my_c_routines.c -o my_c_routines.o
mpifort -c my_fort_routines.f90 -o my_fort_routines.o
mpifort my_c_routines.o my_fort_routines.o -o my_code.x -L$PREFIX/lib -lipmf -lipm
IPM is a portable profiling infrastructure for parallel codes. It provides a low-overhead profile of application performance and resource utilization in a parallel program. Communication, computation, and IO are the primary focus. While the design scope targets production computing in HPC centers, IPM has found use in application development, performance debugging and parallel computing education. The level of detail is selectable at runtime and presented through a variety of text and web reports.
IPM has extremely low overhead, is scalable and easy to use requiring no source code modification. It runs on Cray XT/XE, IBM Blue Gene, most Linux clusters using MPICH/OPENMPI, SGI Altix and some NEC machines. IPM is available under an Open Source software license (LGPL). It is currently installed on several Teragrid, Department of Energy, and other supercomputing resources.
IPM brings together several types of information important to developers and users of parallel HPC codes. The information is gathered in a way the tries to minimize the impact on the running code, maintaining a small fixed memory footprint and using minimal amounts of CPU. When the profile is generated the data from individual tasks is aggregated in a scalable way.
IPM is modular. You can measure just what you want. In addition to the core timings and benchmarking data, IPM currently delivers the following modules:
- MPI: Communication topology and statistics for each MPI call and buffer size.
- HPM: FLOPs and such via PAPI on-chip event counters.
- OpenMP: thread level details about load imbalance.
- Memory: memory high watermark, getrusage, sbrk.
- **Switch:**Communication volume and packet loss.
- File I/O: Data written to and read from disk.
- GPU: Memory copied in/out of the GPU and time in kernels.
- Power: Joules of energy consumed by the app.
The 'integrated' in IPM is multi-faceted. It refers to combining the above information together through a common interface and also the integration of the records from all the parallel tasks into a single report. At a high level we seek to integrate together the information useful to all stakeholders in HPC into a common interface that enables a deeper understanding. This includes application developers, science teams using applications, HPC managers, and system architects.
The following are known issues affecting the current master branch of IPM:
VPATHbuilds are not yet supported