mpi_leave_pinned didn't help still at ~145MB/sec
btl_sm_eager_limit from 4096 to 8192 pushes me upto ~212MB/sec, but
pushing it past that doesn't change it anymore
Are there any intelligent programs that can go through and test all
the different permutations of tunables for openmpi? Outside of me
just writing an ugly looping script...
On Wed, Jul 29, 2009 at 1:55 PM, Dorian Krause<doriankrause_at_[hidden]> wrote:
> --mca mpi_leave_pinned 1
> might help. Take a look at the FAQ for various tuning parameters.
> Michael Di Domenico wrote:
>> I'm not sure I understand what's actually happened here. I'm running
>> IMB on an HP superdome, just comparing the PingPong benchmark
>> HP-MPI v2.3
>> Max ~ 700-800MB/sec
>> OpenMPI v1.3
>> -mca btl self,sm - Max ~ 125-150MB/sec
>> -mca btl self,tcp - Max ~ 500-550MB/sec
>> Is this behavior expected? Are there any tunables to get the OpenMPI
>> sockets up near HP-MPI?
>> users mailing list
> users mailing list