Complete Intel MPI Benchmarks (IMB) keyboard shortcuts and commands reference — 12 shortcuts across 3 categories. Quick reference cheat sheet for Windows & Mac.
The Intel MPI Benchmarks are the other standard set beside OSU for measuring an MPI library and its network, and IMB-MPI1 covers point-to-point and collective patterns in one binary selected by argument. The table lists the common invocations; the notes explain what each pattern isolates and the flags that keep a run focused.
| Shortcut | Action | Description |
|---|---|---|
| mpirun -np 2 IMB-MPI1 PingPong | PingPong test | Measure point-to-point latency and bandwidth between two ranks. |
| mpirun -np 2 IMB-MPI1 PingPing | PingPing test | Measure bidirectional latency with both ranks sending simultaneously. |
| mpirun -np 4 IMB-MPI1 Sendrecv | Sendrecv test | Measure bandwidth in a periodic ring communication pattern. |
| mpirun -np 4 IMB-MPI1 Exchange | Exchange test | Measure bandwidth when each rank exchanges data with both neighbors. |
| Shortcut | Action | Description |
|---|---|---|
| mpirun -np 8 IMB-MPI1 Allreduce | Allreduce test | Benchmark the MPI_Allreduce collective operation. |
| mpirun -np 8 IMB-MPI1 Allgather | Allgather test | Benchmark the MPI_Allgather collective operation. |
| mpirun -np 8 IMB-MPI1 Alltoall | Alltoall test | Benchmark the MPI_Alltoall collective operation. |
| mpirun -np 8 IMB-MPI1 Bcast | Broadcast test | Benchmark the MPI_Bcast collective operation. |
| mpirun -np 8 IMB-MPI1 Barrier | Barrier test | Benchmark MPI_Barrier synchronization overhead. |
| Shortcut | Action | Description |
|---|---|---|
| -msglog min:max | Set message size range | Set transfer sizes as powers of two, e.g. 2:16 for 4 bytes up to 64KB. |
| -include name | Include benchmark | Add a specific benchmark to the run alongside the defaults. |
| -npmin n | Minimum process count | Set the minimum number of active processes for a benchmark. |
The most essential Intel MPI Benchmarks (IMB) shortcuts are: mpirun -np 2 IMB-MPI1 PingPong (PingPong test), mpirun -np 2 IMB-MPI1 PingPing (PingPing test), mpirun -np 4 IMB-MPI1 Sendrecv (Sendrecv test).
These are command-line commands — type them in your terminal or console. Combine them with shell history search (Ctrl + R) and aliases to work even faster.
The Intel MPI Benchmarks (IMB) shortcut for pingpong test is mpirun -np 2 IMB-MPI1 PingPong. Measure point-to-point latency and bandwidth between two ranks.
Intel MPI Benchmarks (IMB) includes 4 Single Transfer (IMB-MPI1) shortcuts, including mpirun -np 2 IMB-MPI1 PingPong (PingPong test) and mpirun -np 2 IMB-MPI1 PingPing (PingPing test). See the full list in the Single Transfer (IMB-MPI1) section above.
Yes — use My Stack to combine Intel MPI Benchmarks (IMB) shortcuts with any other platform on this site into one printable reference, which is useful if your daily workflow spans several tools.
mpirun -np 2 IMB-MPI1 PingPong is the classic latency and bandwidth test between two ranks — place them on different nodes to measure the network, on the same node to measure shared memory — and its small-message time is the fabric's latency. mpirun -np 2 IMB-MPI1 PingPing sends both ways at once, and mpirun -np 4 IMB-MPI1 Sendrecv and mpirun -np 4 IMB-MPI1 Exchange run ring patterns that show how bandwidth holds up under bidirectional load.
mpirun -np 8 IMB-MPI1 Allreduce is the pattern behind gradient synchronisation and the one to watch for training clusters; mpirun -np 8 IMB-MPI1 Allgather, mpirun -np 8 IMB-MPI1 Alltoall and mpirun -np 8 IMB-MPI1 Bcast cover the rest, and mpirun -np 8 IMB-MPI1 Barrier measures pure synchronisation cost. Each benchmark prints a table per message size with min, max and average time; the gap between min and max at large process counts reveals stragglers.
-msglog min:max restricts message sizes to powers of two in that range, so a run can focus on the small-message regime or the bandwidth regime. -include name adds benchmarks to the default list and -npmin n sets the smallest process count to test; by default IMB runs each collective at several process counts up to the launch size, which is how scaling curves are produced in one job. Placement and binding flags on mpirun apply as they would to any job.
Open your assistant with this page preloaded as the source — great for follow-up questions like "which of these work in other apps?"