Re: [OMPI users] No more default core binding since 2.0.2?

2017-04-09 Thread r...@open-mpi.org
Let me try to clarify. If you launch a job that has only 1 or 2 processes in it (total), then we bind to core by default. This is done because a job that small is almost always some kind of benchmark. If there are more than 2 processes in the job (total), then we default to binding to NUMA (if

Re: [OMPI users] No more default core binding since 2.0.2?

2017-04-09 Thread Reuti
>> But I can't see a binding by core for number of processes <= 2. Does it mean >> 2 per node or 2 overall for the `mpiexec`? > > It’s 2 processes overall Having a round-robin allocation in the cluster, this might not be what was intended (to bind only one or two cores per exechost)? Obviousl

Re: [OMPI users] No more default core binding since 2.0.2?

2017-04-09 Thread r...@open-mpi.org
> On Apr 9, 2017, at 1:49 PM, Reuti wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > Am 09.04.2017 um 16:35 schrieb r...@open-mpi.org : > >> There has been no change in the policy - however, if you are oversubscribed, >> we did fix a bug to ens

Re: [OMPI users] No more default core binding since 2.0.2?

2017-04-09 Thread Reuti
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Am 09.04.2017 um 16:35 schrieb r...@open-mpi.org: > There has been no change in the policy - however, if you are oversubscribed, > we did fix a bug to ensure that we don’t auto-bind in that situation > > Can you pass along your cmd line? So far

Re: [OMPI users] No more default core binding since 2.0.2?

2017-04-09 Thread r...@open-mpi.org
There has been no change in the policy - however, if you are oversubscribed, we did fix a bug to ensure that we don’t auto-bind in that situation Can you pass along your cmd line? So far as I can tell, it still seems to be working. > On Apr 9, 2017, at 3:40 AM, Reuti wrote: > > Hi, > > While

[OMPI users] No more default core binding since 2.0.2?

2017-04-09 Thread Reuti
Hi, While I noticed an automatic core binding in Open MPI 1.8 (which in a shared cluster may lead to oversubscribing of cores), I can't spot this any longer in the 2.x series. So the question arises: - Was this a general decision to no longer enable automatic core binding? First I thought it m