Using MPI with IPython¶
Often, a parallel algorithm will require moving data between the engines. One way of accomplishing this is by doing a pull and then a push using the multiengine client. However, this will be slow as all the data has to go through the controller to the client and then back through the controller, to its final destination.
A much better way of moving data between engines is to use a message passing library, such as the Message Passing Interface (MPI) [MPI]. IPython’s parallel computing architecture has been designed from the ground up to integrate with MPI. This document describes how to use MPI with IPython.
Additional installation requirements¶
If you want to use MPI with IPython, you will need to install:
The mpi4py package is not a strict requirement. However, you need to
have some way of calling MPI from Python. You also need some way of
making sure that
MPI_Init() is called when the IPython engines start
up. There are a number of ways of doing this and a good number of
associated subtleties. We highly recommend just using mpi4py as it
takes care of most of these problems. If you want to do something
different, let us know and we can help you get started.
Starting the engines with MPI enabled¶
To use code that calls MPI, there are typically two things that MPI requires.
- The process that wants to call MPI must be started using mpiexec or a batch system (like PBS) that has MPI support.
- Once the process starts, it must call
There are a couple of ways that you can start the IPython engines and get these things to happen.
Automatic starting using mpiexec and ipcluster¶
The easiest approach is to use the MPI Launchers in ipcluster, which will first start a controller and then a set of engines using mpiexec:
$ ipcluster start -n 4 --engines=MPIEngineSetLauncher
This approach is best as interrupting ipcluster will automatically stop and clean up the controller and engines.
Manual starting using mpiexec¶
If you want to start the IPython engines using the mpiexec, just do:
$ mpiexec -n 4 ipengine --mpi=mpi4py
This requires that you already have a controller running and that the FURL files for the engines are in place. We also have built in support for PyTrilinos [PyTrilinos], which can be used (assuming is installed) by starting the engines with:
$ mpiexec -n 4 ipengine --mpi=pytrilinos
Actually using MPI¶
Once the engines are running with MPI enabled, you are ready to go. You can now call any code that uses MPI in the IPython engines. And, all of this can be done interactively. Here we show a simple example that uses mpi4py [mpi4py] version 1.1.0 or later.
First, lets define a simply function that uses MPI to calculate the sum of a
distributed array. Save the following text in a file called
from mpi4py import MPI import numpy as np def psum(a): locsum = np.sum(a) rcvBuf = np.array(0.0,'d') MPI.COMM_WORLD.Allreduce([locsum, MPI.DOUBLE], [rcvBuf, MPI.DOUBLE], op=MPI.SUM) return rcvBuf
Now, start an IPython cluster:
$ ipcluster start --profile=mpi -n 4
It is assumed here that the mpi profile has been set up, as described here.
Finally, connect to the cluster and use this function interactively. In this
case, we create a distributed array and sum up all its elements in a distributed
manner using our
In : from IPython.parallel import Client In : c = Client(profile='mpi') In : view = c[:] In : view.activate() # enable magics # run the contents of the file on each engine: In : view.run('psum.py') In : view.scatter('a',np.arange(16,dtype='float')) In : view['a'] Out: [array([ 0., 1., 2., 3.]), array([ 4., 5., 6., 7.]), array([ 8., 9., 10., 11.]), array([ 12., 13., 14., 15.])] In : %px totalsum = psum(a) Parallel execution on engines: [0,1,2,3] In : view['totalsum'] Out: [120.0, 120.0, 120.0, 120.0]
Any Python code that makes calls to MPI can be used in this manner, including compiled C, C++ and Fortran libraries that have been exposed to Python.
|[MPI]||Message Passing Interface. http://www-unix.mcs.anl.gov/mpi/|
|[mpi4py]||(1, 2) MPI for Python. mpi4py: http://mpi4py.scipy.org/|
|[OpenMPI]||Open MPI. http://www.open-mpi.org/|