Intel® MPI Library

Tuning with mpitune Utility

Besides the standard capabilities for compiling and running MPI applications, Intel® MPI Library provides an automatic utility for optimizing Intel MPI Library parameters for a particular cluster or application. This utility is called mpitune and is available in the <installdir>\intel64\bin directory.

Compiler Command Options

-static_mpi

Use this option to link the Intel® MPI Library statically. This option does not affect the default linkage method for other libraries.

-static

Use this option to link the Intel® MPI Library statically. This option is passed to the compiler.

-nostrip

Use this option to turn off the debug information stripping while linking the Intel® MPI Library statically.

Using Checkpoint-Restart

The checkpoint-restart feature is available with the Hydra process launcher (mpiexec.hydra) or its wrapper (mpirun). The launcher provides two mutually exclusive methods of taking checkpoints:

  • By timers

  • By an explicit signal

You can provide directory paths where checkpoints can be stored temporarily and permanently.

ILP64 Support

The term ILP64 means that integer, long, and pointer data entities all occupy 8 bytes. This differs from the more conventional LP64 model in which only long and pointer data entities occupy 8 bytes while integer entities occupy 4 bytes. More information on the historical background and the programming model philosophy can be found, for example, in http://www.unix.org/version2/whatsnew/lp64_wp.html

Compiler Commands

(SDK only)

The following table lists the available Intel® MPI Library compiler commands with their underlying compilers and programming languages.

Table 2.1-1 Intel® MPI Library Compiler Wrappers

Compiler Command

Underlying Compiler

Supported Language(s)

Common Compilers

ILP64 Support

The term ILP64 means that integer, long, and pointer data entities all occupy 8 bytes. This differs from the more conventional LP64 model in which only long and pointer data entities occupy 8 bytes while integer entities occupy 4 bytes. More information on the historical background and the programming model philosophy can be found, for example, in http://www.unix.org/version2/whatsnew/lp64_wp.html

GDB*: The GNU* Project Debugger

Use the following command to launch the GDB* debugger with Intel® MPI Library:

$ mpirun -gdb -n 4 ./testc

You can work with the GDB debugger as you usually do with a single-process application. For details on how to work with parallel programs, see the GDB documentation at http://www.gnu.org/software/gdb/.

You can also attach to a running job with:

$ mpirun -n 4 -gdba <pid>

Where <pid> is the process ID for the running MPI process.

Subscribe to Intel® MPI Library