Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

Subject: [OMPI users] mpirun with -am ft-enable-cr option takes longer time on certain configurations
From: ananda.mudar_at_[hidden]
Date: 2010-03-20 23:14:50

I am observing a very strange performance issue with my openmpi program.


I have compute intensive openmpi based application that keeps the data
in memory, process the data and then dumps it to GPFS parallel file
system. GPFS parallel file system server is connected to a QDR
infiniband switch from Voltaire.


If my cluster is connected to a DDR infiniband switch which in turn
connects to file system server on QDR switch, I see that I can run my
application under checkpoint/restart control (with -am ft-enable-cr) and
I can checkpoint (ompi-checkpoint) successfully and the application gets
completed after few additional seconds.


If my cluster is connected to the same QDR switch which connects to file
system server, I see that my application takes close to 10x time to
complete if I run it under checkpoint/restart control (with -am
ft-enable-cr). If I run the same application using a plain mpirun
command (ie; without -am ft_enable_cr), it finishes within a minute.


I am using open mpi 1.3.4 and BLCR 0.8.2 for checkpointing


Are there any specific MCA parameters that I should tune to address this
problem? Any other pointers will be really helpful.




Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.