I see your point, but I don't know how to make that happen. The problem is
that spawn really should fail under certain conditions because you asked us
to do something we couldn't do - i.e., you asked that we launch and bind
more processes then we could. Increasing the number of available resources
Hi Ralph,
On 2014/06/25 2:51, Ralph Castain wrote:
> Had a chance to review this with folks here, and we think that having
> oversubscribe automatically set overload makes some sense. However, we do
> want to retain the ability to separately specify oversubscribe and overload
> as well since these
Hi Gilles
Had a chance to review this with folks here, and we think that having
oversubscribe automatically set overload makes some sense. However, we do
want to retain the ability to separately specify oversubscribe and overload
as well since these two terms don't mean quite the same thing.
Our
Folks,
this issue is related to the failures reported by mtt on the trunk when
the ibm test suite invokes MPI_Comm_spawn.
my test bed is made of 3 (virtual) machines with 2 sockets and 8 cpus
per socket each.
if i run on one host (without any batch manager)
mpirun -np 16 --host slurm1 --oversub
