Jeff,
Thank you for your thoughts. Some more comments inlined.
Regards,
--Oleg
On 10/9/07, Jeff Squyres wrote:
>
> Interesting idea.
>
> One obvious solution would be to mpirun your controller tasks and, as
> you mentioned, use MPI to communicate between them. Then you can use
> MPI_COMM_SPAWN
Interesting idea.
One obvious solution would be to mpirun your controller tasks and, as
you mentioned, use MPI to communicate between them. Then you can use
MPI_COMM_SPAWN to launch the actual MPI job that you want to monitor.
However, this will only more-or-less work. OMPI currently poll
Hello Oleg :-)
I am a newbie as far as MPI is concerned. Still I will take a shot:
On 10/2/07, Oleg Morajko wrote:
> Hello,
>
> In the context of my PhD research, I have been developing a run-time
> performance analyzer for MPI-based applications.
> My tool provides a controller process for each
Hello,
In the context of my PhD research, I have been developing a run-time
performance analyzer for MPI-based applications.
My tool provides a controller process for each MPI task. In particular, when
a MPI job is started, a special wrapper script is generated that first
starts my controller proc