I am looking for some pointers for obtaining optimal performance on the
lam-mpi installation on a single 2p G5 system. The default install installed
the rpi module sysv. However I am getting very poor latency numbers from two
mpi tasks on a single node, which leads me to believe the message-passing is
not using the shared-memory and rather going out to the switch for on-node
communication.
leapfrog<3>laminfo
LAM/MPI: 7.0.2
Prefix: /usr/local/lam-mpi
Architecture: powerpc-apple-darwin6.7.5
Configured by: root
Configured on: Thu Oct 9 15:05:20 CDT 2003
Configure host: leapfrog.tacc.utexas.edu
C bindings: yes
C++ bindings: yes
Fortran bindings: yes
C profiling: yes
C++ profiling: yes
Fortran profiling: yes
ROMIO support: no
IMPI support: no
Debug support: no
Purify clean: no
SSI boot: globus (Module v0.5)
SSI boot: rsh (Module v1.0)
SSI coll: lam_basic (Module v7.0)
SSI coll: smp (Module v1.0)
SSI rpi: crtcp (Module v1.0)
SSI rpi: lamd (Module v7.0)
SSI rpi: sysv (Module v7.0)
SSI rpi: tcp (Module v7.0)
SSI rpi: usysv (Module v7.0)
When I am forcing lamboot to boot up the module sysv, I get the following:
leapfrog<6>lamboot -v -ssi rpi sysv bhost
LAM 7.0.2/MPI 2 C++ - Indiana University
n0<1781> ssi:boot:base:linear: booting n0 (localhost)
n0<1781> ssi:boot:base:linear: finished
Any suggestion(s) is greatly appreciated.
Thanks
-- Avi
|
