Re: [OMPI users] Oversubscribing in 1.8.3 vs 1.6.5

On 12/09/2014 04:19 PM, Nathan Hjelm wrote: yield when idle is broken on 1.8. Fixing now. ok, thanks a lot! will wait for the fix! Eric

Re: [OMPI users] Oversubscribing in 1.8.3 vs 1.6.5

yield when idle is broken on 1.8. Fixing now. -Nathan On Tue, Dec 09, 2014 at 01:02:08PM -0800, Ralph Castain wrote: > Hmmm….well, it looks like we are doing the right thing and running unbound > when oversubscribed like this. I don’t have any brilliant idea why it would > be running so

Re: [OMPI users] Oversubscribing in 1.8.3 vs 1.6.5

Hmmm….well, it looks like we are doing the right thing and running unbound when oversubscribed like this. I don’t have any brilliant idea why it would be running so slowly in that situation when compared with 1.6.5 - it could be that yield-when-idle is borked. I’ll try to dig into that notion a

Re: [OMPI users] Oversubscribing in 1.8.3 vs 1.6.5

Hi again, I sorted and "seded" (cat outpout.1.00 |sed 's/default/default value/g'|sed 's/true/1/g' |sed 's/false/0/g') the output.1.00 file from: mpirun --output-filename output -mca mpi_show_mca_params all --report-bindings -np 32 myprog between a launch with 165 vs 183. The diff may be

Re: [OMPI users] Oversubscribing in 1.8.3 vs 1.6.5

On 12/09/2014 12:24 PM, Ralph Castain wrote: Can you provide an example cmd line you use to launch one of these tests using 1.8.3? Some of the options changed between the 1.6 and 1.8 series, and we bind by default in 1.8 - the combination may be causing you a problem. I very simply launch:

Re: [OMPI users] Oversubscribing in 1.8.3 vs 1.6.5

Not for that many procs - we default to binding to socket for anything more than 2 procs > On Dec 9, 2014, at 9:24 AM, Nathan Hjelm wrote: > > > One thing that changed between 1.6 and 1.8 is the default binding > policy. Open MPI 1.6 did not bind by default but 1.8 binds to

Re: [OMPI users] Oversubscribing in 1.8.3 vs 1.6.5

Can you provide an example cmd line you use to launch one of these tests using 1.8.3? Some of the options changed between the 1.6 and 1.8 series, and we bind by default in 1.8 - the combination may be causing you a problem. > On Dec 9, 2014, at 9:14 AM, Eric Chamberland >

Re: [OMPI users] Oversubscribing in 1.8.3 vs 1.6.5

One thing that changed between 1.6 and 1.8 is the default binding policy. Open MPI 1.6 did not bind by default but 1.8 binds to core. You can unset the binding policy by adding --bind-to none. -Nathan Hjelm HPC-5, LANL On Tue, Dec 09, 2014 at 12:14:32PM -0500, Eric Chamberland wrote: > Hi, > >

[OMPI users] Oversubscribing in 1.8.3 vs 1.6.5

Hi, we were used to do oversubscribing just to do code validation in nightly automated parallel runs of our code. I just compiled openmpi 1.8.3 and launched the whole suit of sequential/parallel tests and noticed a *major* slowdown in oversubscribed parallel tests with 1.8.3 compared to

[OMPI users] open mpi and MLX

I am having a trouble running simple benchmarks like osu bidirectional bandwidth tests with recent OMPI (> version 1.8.1)over MLX. All versions including 1.8.1 seem to work. The issue is that FDR will hang frequently and will complain about physical memory available for user run is very low.

Re: [OMPI users] Cannot open configuration file - openmpi/mpic++-wrapper-data.txt

Hi Reuti, Thanks for your quick help. It works as required when setting OPAL_PREFIX variable to the current installation path. Thanks once again. -- regards, Manoj Vaghela On Tue, Dec 9, 2014 at 1:50 PM, Reuti wrote: > Hi, > > please have a look here: > >

Re: [OMPI users] Cannot open configuration file - openmpi/mpic++-wrapper-data.txt

Hi, please have a look here: http://www.open-mpi.org/faq/?category=building#installdirs -- Reuti Am 09.12.2014 um 07:26 schrieb Manoj Vaghela: > Hi OpenMPI Users, > > I am trying to build OpenMPI libraries using standard configuration and > compile procedure. It is just the one thing that

[OMPI users] Cannot open configuration file - openmpi/mpic++-wrapper-data.txt

Hi OpenMPI Users, I am trying to build OpenMPI libraries using standard configuration and compile procedure. It is just the one thing that I want to install all in a user specified path like following: OMPI_DIR is something like $HOME/Shared_Build/openmpi-1.8.3 [OMPI_DIR] $ ./configure