I found a fun head scratcher, with openmpi 1.8.2 with torque 5 built with TM
support, on hereto core layouts I get the fun thing:
mpirun -report-bindings hostname< Works
mpirun -report-bindings -np 64 hostname <- Wat?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 23.09.2014 um 19:53 schrieb Brock Palen:
> I found a fun head scratcher, with openmpi 1.8.2 with torque 5 built with TM
> support, on hereto core layouts I get the fun thing:
> mpirun -report-bindings hostname< Works
And you get
Hi,
Just an idea here. Do you use cpusets within Torque ? Did you request
enough cores to torque ?
Maxime Boissonneault
Le 2014-09-23 13:53, Brock Palen a écrit :
I found a fun head scratcher, with openmpi 1.8.2 with torque 5 built with TM
support, on hereto core layouts I get the fun thin
FWIW: that warning has been removed from the upcoming 1.8.3 release
On Sep 23, 2014, at 11:45 AM, Reuti wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am 23.09.2014 um 19:53 schrieb Brock Palen:
>
>> I found a fun head scratcher, with openmpi 1.8.2 with torque 5 built with
>>
Yes the request to torque was procs=64,
We are using cpusets.
the mpirun without -np 64 creates 64 spawned hostnames.
Brock Palen
www.umich.edu/~brockp
CAEN Advanced Computing
XSEDE Campus Champion
bro...@umich.edu
(734)936-1985
On Sep 23, 2014, at 3:02 PM, Ralph Castain wrote:
> FWIW: th
Do you know the topology of the cores allocated by Torque (i.e. were
they all on the same nodes, or 8 per node, or a heterogenous
distribution for example ?)
Le 2014-09-23 15:05, Brock Palen a écrit :
Yes the request to torque was procs=64,
We are using cpusets.
the mpirun without -np 64 c
