ALIs
kommt nochmpiP: Lightweight, Scalable MPI Profiling
Introduction
mpiP is a lightweight profiling library for MPI applications. Because it only collects statistical information about MPI functions, mpiP generates considerably less overhead and much less data than tracing tools. All the information captured by mpiP is task-local. It only uses communication during report generation, typically at the end of the experiment, to merge results from all of the tasks into one output file. Using mpiP is very simple. Because it gathers MPI information through the MPI profiling layer, mpiP is a link-time library.
Installation on LRZ HPC platforms
| mpiP Release | Platform |
|---|---|
|
3.3 |
SuperMIG, MPP Cluster, ICE Cluster and UV Cluster |
Usage
Before using mpiP, it is necessary to load the appropriate environment module:
module add mpip
and recompile adding the mpiP library, also add the '-g' option. in order to decode the performance counter to a source code filename and line number automaticall with mpiP.
mpicc $MPIP_LIB -g -o foo foo.c
Application profiling
Run your application as usual
You can verify that mpiP is working by identifying the header and trailer in standard out.
mpiP: mpiP: mpiP: mpiP V3.3 (Build Jul 25 2008/11:28:38) mpiP: Direct questions and errors to mpip-help@lists.sourceforge.net mpiP: mpiP: mpiP: Storing mpiP output in [./foo.4.8483.1.mpiP]. mpiP:
By default, the output file is written to the current directory of the application. mpiP files are always much smaller than trace files, so writing them to this directory is safe.