Jeff,
Thanks for the detailed discussion. It certainly makes things a lot clearer,
just as I was giving up my hopes for a reply.
The app is fairly heavy on communication (~10k messages per minute) and is
also embarrassingly parallel. Taking this into account, I think I'll
readjust my resilience ex
It certainly does make sense to use MPI for such a setup. But there
are some important things to consider:
1. MPI, at its heart, is a communications system. There's lots of
other bells and whistles (e.g., starting up a whole bunch of processes
in tandem), but at the core: it's all about p
Hi, although I did my due diligence on searching for this question,
I apologise if this is a repeat.
>From an architectural point of view does it make sense to use MPI in the
following scenario (for the purposes of resilience as much as
parallelization):
Each process is a long-running process (run
