topic This issue is now closed. If in Intel® MPI Library

Process tracing

youn__kihang — Thu, 23 Jan 2020 07:21:59 GMT

Hello,

I am going to test the difference between mpirun and mpiexec on LSF.
The following manual says that mpirun is related to LSF.
(https://software.intel.com/en-us/mpi-developer-reference-linux-mpirun)

1. I would like to see what physical process mpirun and mpiexec use when working through LSF.
Can the "-trace" command confirm which physical processes are being used?

2. Since there is a case where mpiexec is faster, I want to use mpiexec instead of mpirun.
Is there a disadvantage of not being recognized by job scheduler?

Thanks

Hi,

PrasanthD_intel — Fri, 24 Jan 2020 11:11:57 GMT

Hi,

Thanks for reaching out to us.

We will get back to you soon.

Prasanth

HI,

Anatoliy_R_Intel — Mon, 27 Jan 2020 07:17:07 GMT

HI,

What do you mean by physical processes? Anyway, mpirun is just a wrapper for mpiexec to automatically detect job schedulers. Since Intel MPI 2019, mpiexec can also automatically detect job schedulers. In Intel MPI 2018 only mpirun could do this. So, now you can use just mpiexec.

Best regards, Anatoliy

Please use "export I_MPI

Klaus-Dieter_O_Intel — Tue, 28 Jan 2020 23:41:40 GMT

Please use "export I_MPI_DEBUG=5" in your LSF script to see which processors are used per node.

The flag "-trace" is used to create trace files for the Intel Trace Analyzer and Collector, see https://software.intel.com/en-us/trace-analyzer, i.e. to profile the MPI communication in your code.

This issue is now closed. If

Klaus-Dieter_O_Intel — Fri, 15 May 2020 16:44:17 GMT

This issue is now closed. If you have a similar question, please start a new thread.