Hi Matthias,

You might want to play with process binding to see if your problem is related to bad memory affinity.

Try to launch pingpong on two CPUs of the same socket, then on different sockets (i.e. bind each process to a core, and try different configurations).

Sylvain



De :        Matthias Jurenz <matthias.jurenz@tu-dresden.de>
A :        Open MPI Developers <devel@open-mpi.org>
Date :        13/02/2012 12:12
Objet :        [OMPI devel] poor btl sm latency
Envoyé par :        devel-bounces@open-mpi.org




Hello all,

on our new AMD cluster (AMD Opteron 6274, 2,2GHz) we get very bad latencies
(~1.5us) when performing 0-byte p2p communication on one single node using the
Open MPI sm BTL. When using Platform MPI we get ~0.5us latencies which is
pretty good. The bandwidth results are similar for both MPI implementations
(~3,3GB/s) - this is okay.

One node has 64 cores and 64Gb RAM where it doesn't matter how many ranks
allocated by the application. We get similar results with different number of
ranks.

We are using Open MPI 1.5.4 which is built by gcc 4.3.4 without any special
configure options except the installation prefix and the location of the LSF
stuff.

As mentioned at
http://www.open-mpi.org/faq/?category=sm we tried to use
/dev/shm instead of /tmp for the session directory, but it had no effect.
Furthermore, we tried the current release candidate 1.5.5rc1 of Open MPI which
provides an option to use the SysV shared memory (-mca shmem sysv) - also this
results in similar poor latencies.

Do you have any idea? Please help!

Thanks,
Matthias
_______________________________________________
devel mailing list
devel@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel