Intel® MPI Library
Get help with building, analyzing, optimizing, and scaling high-performance computing (HPC) applications.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
2275 Discussions

Tracing MPI call with Intel MPI

dsi-intel_d_
Beginner
‎09-08-2014 05:59 AM
724 Views

Hi,

Is there a way to trace MPI calls (meaning: each time an MPI function is called, I'd like to see the function name, parameters and emitting process) using Intel MPI ?

There is a --trace option, but it seems connected with Trace Analyzer which only seems able to print information regarding cumulated time spent in a given function ?

I've been trying to read the documentation for some time now, and it does not seems to be supported, which seems kind of strange...

 

Regards,

0 Kudos

Link Copied

1 Reply
James_T_Intel
Moderator
‎09-10-2014 07:18 AM
724 Views

Actually, the Intel® Trace Analyzer does report all of that information.  There are several ways to get information from Intel® Trace Analyzer regarding the message information.  If you go to the Event Timeline chart, right click on any of the messages, and click Details on Message.  This gives details such as sender and receiver, message size, and more:

message details.png

Does this help?

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.