1. Overview

The Intel Cluster Toolkit is a collection of MPI related tools, which is helpful when debugging, fine tuning and analyzing large MPI applications. ICT includes:

Intel C++ Compiler 11.1
Intel Debugger 11.1
Intel MPI Library 3.2
Intel MPI Benchmarks 3.2
Intel Trace Analyzer1 and Trace Collector 7.2

2. Using ICT

Each of this parts and its use at the cluster environment in DESY Zeuthen is described next.

2.1. Setting up the environment

Intitialize the Intel compiler and Intel MPI environment:

ini ic openmpi_intel

Initialize ICT environment:

 source /opt/intel/itac/7.2.2.006/bin/itacvars.sh
 source /opt/intel/impi/3.2.2.006/bin/mpivars.sh
 source /opt/products/idb/11.0/bin/ia32/idbvars.sh
 export I_MPI_CC=/opt/products/bin/icc

2.2. Compiling MPI applications with Intel MPI

Add

LDFLAGS     = -L$(VT_LIB_DIR) -lmpi $(VT_ADD_LIBS)

to the IMB Makefile.

2.3. MPD daemons

The first step in setting up the MPD daemons, which are actually the environment for strating the parallel applications, is to set up an SSH connectivity environment with the help of the sshconnectivity.exp script and the imachines.LINUX file. The script is available sshconnectivity.exp.

TODO: mpd.hosts

Start MPD daemons on all hosts in mpd.hosts file:

# ./sshconnectivity.exp machines.LINUX
# mpdboot -n 8 --rsh=ssh -f ./mpd.hosts

2.4. Tracing information

Run an application for the trace analyzer:

# export VT_LOGFILE_FORMAT=STF;
# export VT_PCTRACE=5;
# export VT_PROCESS="0:N ON";
# export VT_LOGFILE_PREFIX=IMB-MPI1_inst;
# rm -fr $VT_LOGFILE_PREFIX; mkdir $VT_LOGFILE_PREFIX;
# mpiexec -n 2 itcpin --run -- ./IMB-MPI1 -npmin 2 PingPong;
# traceanalyzer ./IMB-MPI1_inst/IMB-MPI1.stf &;

After you are done with running and analysing your application shut down the MPD daemons with the command:

# mpdallexit

2.5. Fine tuning

Invoke mpitune:

# mpitune -f machines.LINUX -o ./ --app mpiexec -genv MPIEXEC_DEBUG 1 -n 2 ./IMB-MPI1 -np 2 PingPong
# mpiexec -tune app.conf -n 4 ./IMB-MPI1 -np 2 PingPong

2.6. Debugging

Start execution of the MPI program in debugging mode on 8 nodes each running 2 processes:

# mpiexec -idb -genv MPIEXEC_DEBUG 1 -n 8 ./IMB-MPI1 -np 2 PingPong

-  ⇤ ← Revision 16 as of 2010-06-22 16:20:42 → 
  Size: 2166
  Editor: KonstantinBoyanov
  Comment:
+   ← Revision 17 as of 2010-07-06 14:15:24 → ⇥
  Size: 2450
  Editor: KonstantinBoyanov
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 10:
- * Intel C++ Compiler 11.1 
 * Intel Debugger 11.1 
 * Intel MPI Library 3.2
+ * Intel C++ Compiler 11.1
 * Intel Debugger 11.1
 * Intel MPI Library 3.2
 Line 21:
-{{{#!c 
ini ic openmpi_intel
+{{{#!c
ini ic openmpi_intel
-Line 24:
+Line 25:
+Initialize ICT environment:
-Line 25:
+Line 27:
-Initialize ICT environment:
-Line 32:
+Line 33:
+== Compiling MPI applications with Intel MPI ==
Add
-Line 33:
+Line 36:
-== Compiling MPI applications with Intel MPI ==
Add {{{ LDFLAGS     = -L$(VT_LIB_DIR) -lmpi $(VT_ADD_LIBS) }}} to the IMB Makefile.
+{{{
LDFLAGS     = -L$(VT_LIB_DIR) -lmpi $(VT_ADD_LIBS)
}}}
to the IMB Makefile.
-Line 37:
+Line 42:
-TODO: machines.LINUX file
+The first step in setting up the MPD daemons, which are actually the environment for strating the parallel applications, is to set up an SSH connectivity environment with the help of the sshconnectivity.exp script and the imachines.LINUX file. The script is available [[attachment:sshconnectivity.exp]].
-Line 41:
+Line 47:
-Line 45:
+Line 52:
-Line 48:
+Line 54:
-Line 57:
+Line 64:
+After you are done with running and analysing your application shut down the MPD daemons with the command:
-Line 58:
+Line 66:
-After you are done with running and analysing your application shut down the MPD daemons with the command:
-Line 64:
+Line 71:
-Line 66:
+Line 74:
 # mpiexec -tune app.conf -n 4 ./IMB-MPI1 -np 2 PingPong
-Line 68:
+Line 76:
-Line 71:
+Line 78:

Wiki

Page