Intel® MPI Library

Communication Problems

Communication problems with the Intel® MPI Library are usually caused by a signal termination (SIGTERM, SIGKILL, or other signals). Such terminations may be due to a host reboot, receiving an unexpected signal, out-of-memory (OOM) manager errors and others.

To deal with such failures, you need to find out the reason for the MPI process termination (for example, by checking the system log files).

Configuring a Visual Studio* Project

To configure a Visual Studio* project with Intel® MPI Library, do the following:

  1. In Microsoft* Visual Studio*, create a console application project, or open an existing one.

  2. Open the project properties and go to Configuration Properties > Debugging. Set the following parameters:

    Command: $(I_MPI_ROOT)\intel64\bin\mpiexec.exe
    Command arguments: -n <processes_number> "$(TargetPath)"

Cluster Specific Tuning

The cluster specific mode is intended for tuning Intel® MPI Library for a specific cluster. For finding optimal settings, mpitune uses a benchmarking program: it runs tests several times with different parameters and searches for the best ones. By default, Intel® MPI Benchmarks are used.

To tune Intel MPI Library in the cluster specific mode, do the following:

File System Support

Intel® MPI Library provides loadable shared modules to provide native support for the following file systems:

  • Panasas* ActiveScale* File System (PanFS)

  • Lustre* File System

  • IBM* General Parallel File System* (GPFS*)

Interoperability with OpenMP API


Intel® MPI Library provides an additional environment variable to control process pinning for hybrid MPI/OpenMP* applications. This environment variable is used to define a number of non-overlapping subsets (domains) of logical processors on a node, and a set of rules on how MPI processes are bound to these domains by the following formula: one MPI process per one domain. See the picture below.

Subscribe to Intel® MPI Library