Ah, indeed - if the node where mpirun is executing doesn’t match the compute
nodes, then you must remove that --novm option. Otherwise, we have no way of
knowing what the compute node topology looks like.
> On Sep 3, 2016, at 4:13 PM, Gilles Gouaillardet
> wrote:
>
> George,
>
> If i unders
George,
If i understand correctly, you are running mpirun on dancer, which has
2 sockets, 4 cores per socket and 2 hwthreads per core,
and orted are running on arc[00-08], though the tasks only run on arc00, which
has
2 sockets, 10 cores per socket and 2 hwthreads per core
to me, it looks like O
Interesting - well, it looks like ORTE is working correctly. The map is what
you would expect, and so is planned binding.
What this tells us is that we are indeed binding (so far as ORTE is concerned)
to the correct places. Rank 0 is being bound to 0,8, and that is what the OS
reports. Rank 1 i
$mpirun -np 3 --tag-output --bind-to core --report-bindings
--display-devel-map --mca rmaps_base_verbose 10 true
[dancer.icl.utk.edu:17451] [[41198,0],0]: Final mapper priorities
> [dancer.icl.utk.edu:17451] Mapper: ppr Priority: 90
> [dancer.icl.utk.edu:17451] Mapper: seq Priority: 60
>
Okay, can you add --display-devel-map --mca rmaps_base_verbose 10 to your cmd
line?
It sounds like there is something about that topo that is bothering the mapper
> On Sep 2, 2016, at 9:31 PM, George Bosilca wrote:
>
> Thanks Gilles, that's a very useful trick. The bindings reported by ORTE ar
