mailRe: r3237 - in /branches/multi_processor: multi/mpi4py_processor.py relax


Others Months | Index by Date | Thread Index
>>   [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Header


Content

Posted by Edward d'Auvergne on March 20, 2007 - 14:02:
>> > As MPI
>> > is solely for those who are very serious and have access to clusters,
>>
>> not true! mpi can run over ssh as well. For example lam has an ssh
>> backend and this is what i am using for testing on my computer!
>
>
> MPI can be used for grid computing but that is not what it is designed
> for and hence isn't optimal

why?

That what all the documentation I've read about MPI's limitations have said. By quickly checking on Wikipedia (http://en.wikipedia.org/wiki/Message_Passing_Interface), I just found the following text:

4. Grid computing, and virtual grid computing offer MPIs way of
handling static and dynamic process management with particular 'fits'.
While it is possible for force the MPI model into working on a grid,
the idea of a fault-free, long-running virtual machine under the MPI
program is a forced on in a grid environment. Grids may want to
instantiate MPI APIs between sets of running processes, but
multi-level middleware that addresses concurrency, faults, and message
traffic are needed. Fault tolerant MPI's and Grid MPIs have been
attempted, but the original design of MPI itself impacts what can be
done.

My personal experience with the coding of the grid computing code, I
would assume that there are a number of differences.  For example the
algorithm relax currently uses to handle computers of different
speeds.  Grid computing is designed for a heterogeneous environment
whereas MPI is not.  I'm not saying one is superior to the other but
that they have different applications in different computing
environments.

Cheers,

Edward



Related Messages


Powered by MHonArc, Updated Tue Mar 20 15:00:42 2007