My question is why? If you are willing to reserve a chunk of your
machine for yet-to-exist tasks, why not just create them all at mpirun
time and slice and dice your communicators as appropriate?
On Thu, 2010-01-28 at 09:24 +1100, Jaison Paul wrote:
> Hi, I am just reposting my early query once
It sounds to me a bit like asking to be born before your mother.
Unless I misunderstand the question...
Douglas.
On Thu, Jan 28, 2010 at 09:24:29AM +1100, Jaison Paul wrote:
> Hi, I am just reposting my early query once again. If anyone one can
> give some hint, that would be great.
>
>
, NY 12601
Tele (845) 433-7846 Fax (845) 433-8363
users-boun...@open-mpi.org wrote on 01/27/2010 06:07:43 PM:
> [image removed]
>
> Re: [OMPI users] How to start MPI_Spawn child processes early?
>
> Ralph Castain
>
> to:
>
> Open MPI Users
>
> 01/27/2010
I can't imagine how you would do that - only thing I can think of would be to
start your "child" processes as one job, then start your "parent" processes and
have them do an MPI_Comm_join with the child job.
That said, I can't imagine that comm_spawn is -that- slow to make much
difference to
Hi, I am just reposting my early query once again. If anyone one can
give some hint, that would be great.
Thanks, Jaison
ANU
Jaison Paul wrote:
Hi All,
I am trying to use MPI for scientific High Performance (hpc)
applications. I use MPI_Spawn to create child processes. Is there a
way to
