I am thinking about implementing a wrapper for MPI that imitates OpenMP’s way
of parallelizing for loops.
begin_parallel_region( chunk_size=100 , num_proc=10 );
for( int i=0 ; i<1000 ; i++ )
{
//some computation
}
end_parallel_region();
The code above distributes computation inside the for loop to 10 slave MPI processors.
Upon entering the parallel region, the chunk size and number of slave processors are provided.
Upon leaving the parallel region, the MPI processors are synched and are put idle.
EDITED in response to High Performance Mark.
I have no intention to simulate the OpenMP’s shared memory model.
I propose this because I need it.
I am developing a library that is required to build graphs from mathetical functions.
In these mathetical functions, there often exist for loops like the one below.
for( int i=0 ; i<n ; i++ )
{
s = s + sin(x[i]);
}
So I want to first be able to distribute sin(x[i]) to slave processors and at the end reduce to the single varible just like in OpenMP.
I was wondering if there is such a wrapper out there so that I don’t have to reinvent the wheel.
Thanks.
Yes, you could do this, for specific tasks. But you shouldn’t.
Consider how you might implement this; the begin part would distribute the data, and the end part would bring the answer back:
That constant distribute/gather is a terrible communications burden to sum up a few numbers, and is antithetical to the entire distributed-memory computing model.
To a first approximation, shared memory approaches – OpenMP, pthreads, IPP, what have you – are about scaling computations faster; about throwing more processors at the same chunk of memory. On the other hand, distributed-memory computing is about scaling a computation bigger; about using more resourses, particularly memory, than can be found on a single computer. The big win of using MPI is when you’re dealing with problem sets which can’t fit on any one node’s memory, ever. So when doing distributed-memory computing, you avoid having all the data in any one place.
It’s important to keep that basic approach in mind even when you are just using MPI on-node to use all the processors. The above scatter/gather approach will just kill performance. The more idiomatic distributed-memory computing approach is for the logic of the program to already have distributed the data – that is, your
begin_parallel_regionandend_parallel_regionabove would have already been built into the code above your loop at the very beginning. Then, every loop is justand when you need to exchange data between tasks (or reduce a result, or what have you) then you call the MPI functions to do those specific tasks.