Intel® Trace Analyzer and Collector

Understand MPI application behavior, quickly finding bottlenecks, and achieving high performance for parallel cluster applications

  • Powerful MPI Communications Profiling and Analysis
  • Scalable - Low Overhead & Effective Visualization
  • Flexible to Fit Workflow – Compile, Link or Run

Intel® Trace Analyzer and Collector 9.0 is a graphical tool for understanding MPI application behavior, quickly finding bottlenecks, improving correctness, and achieving high performance for parallel cluster applications based on Intel architecture. Improve weak and strong scaling for small and large applications with Intel Trace Analyzer and Collector.

Benefits:

  • Visualize and understand parallel application behavior
  • Evaluate profiling statistics and load balancing
  • Analyze performance of subroutines or code blocks
  • Learn about communication patterns, parameters, and performance data
  • Identify communication hotspots
  • Decrease time to solution and increase application efficiency

MPI checking

  • A unique MPI Correctness Checker detects deadlocks, data corruption, and errors with MPI parameters, data types, buffers, communicators, point-to-point messages and collective operations.
  • The Correctness Checker allows the user to scale to extremely large systems and detect errors even among a large number of processes.

Interface and Displays

  • Intel® Trace Analyzer and Collector includes full-color customizable GUI with many drill-down view options.
  • The analyzer is able to extremely rapidly unwind the call stack and use debug information to map instruction addresses to source code.
  • With both command-line and GUI interfaces, the user can additionally set up batch runs or do interactive debugging.

Scalability

  • Low overhead allows random access to portions of a trace, making it suitable for analyzing large amounts of performance data.
  • Thread safety allows you to trace multithreaded MPI applications for event-based tracing as well as non-MPI threaded applications.

Instrumentation and Tracing

  • Low-intrusion instrumentation supports MPI applications with C, C++, or Fortran.
  • Intel Trace Analyzer and Collector automatically records performance data from parallel threads in C, C++, or Fortran

What’s new

  • MPI Communications Profile Summary Overview
    • Quickly Understand Computation vs Communications
    • Identify which MPI communications are being most used
    • Advice of where to start your analysis

  • Expanded Standards Support with MPI 3.0
    • Automated MPI Communications Analysis with Performance Assistant
    • Detect common MPI performance issues
    • Automated tips on potential solutions

Videos to help you get started.

Register for future Webinars


Previously recorded Webinars:

  • Increase Cluster MPI Application Performance with a "MPI Tune" Up
  • MPI on Intel® Xeon Phi™ coprocessor
  • Quickly discover performance issues with the Intel® Trace Analyzer and Collector 9.0 Beta

More Tech Articles

Using Intel® MPI Library 5.0 with MPICH based applications
By Dmitry Sivkov (Intel)Posted 08/25/20140
Why it is needed? Different MPI implementations have their specific benefits and advantages. So in the specific cluster environment the HPC application with the other MPI implementation can probably perform better.  Intel® MPI Library has the following benefits: Support of the wide range of cl...
Intel® Cluster Tools Open Source Downloads
By Gergana Slavova (Intel)Posted 03/06/20140
This article makes available third-party libraries and sources that were used in the creation of Intel® Software Development Products. Intel provides this software pursuant to their applicable licenses. Products and Versions: Intel® Trace Analyzer and Collector for Linux* gcc-3.2.3-42.zip (whi...
Using the Intel® MPI Library on Intel® Xeon Phi™ Coprocessor Systems
By loc-nguyen (Intel)Posted 03/19/201316
Download Article Download Using the Intel® MPI Library on Intel® Xeon Phi™ Coprocessor Systems [PDF 499KB] Table of Contents Chapter 1 – Introduction 1.1 – Overview 1.2 – Compatibility Chapter 2 – Installing the Intel® MPI Library 2.1 – Installing the Intel MPI Library 2.2 – Preparation Chapter 3...
Intel® Trace Collector Filtering
By James Tullos (Intel)Posted 03/14/20130
Filtering in the Intel® Trace Collector will apply specified filters to the trace collection process.  This directly reduces the amount of data collected.  The filter rules can be applied either via command line arguments or in a configuration file (specified by the environment variable VT_CONFIG...
Subscribe to Intel Developer Zone Articles

Supplemental Documentation

Intel® Parallel Studio XE 2015 Update 2 Cluster Edition Readme
By Gergana Slavova (Intel)Posted 02/06/20150
The Intel® Parallel Studio XE 2015 Update 2 Cluster Edition for Linux* and Windows* combines all Intel® Parallel Studio XE and Intel® Cluster Tools into a single package. This multi-component software toolkit contains the core libraries and tools to efficiently develop, optimize, run, and distrib...
Intel® Parallel Studio XE 2015 Update 1 Cluster Edition Readme
By Gergana Slavova (Intel)Posted 11/24/20140
The Intel® Parallel Studio XE 2015 Update 1 Cluster Edition for Linux* and Windows* combines all Intel® Parallel Studio XE and Intel® Cluster Tools into a single package. This multi-component software toolkit contains the core libraries and tools to efficiently develop, optimize, run, and distrib...
Intel® Parallel Studio XE 2015 Cluster Edition Initial Release Readme
By Gergana Slavova (Intel)Posted 08/15/20140
The Intel® Parallel Studio XE 2015 Cluster Edition for Linux* and Windows* combines all Intel® Parallel Studio XE and Intel® Cluster Tools into a single package. This multi-component software toolkit contains the core libraries and tools to efficiently develop, optimize, run, and distribute paral...
Intel® Trace Analyzer and Collector 8.1 Update 3 Readme
By Gergana Slavova (Intel)Posted 08/13/20130
The Intel® Trace Analyzer and Collector 8.1 Update 3 for Linux* and Windows* is a low-overhead scalable event-tracing library with graphical analysis that reduces the time it takes an application developer to enable maximum performance of cluster applications. This package is for users who dev...
Subscribe to Intel Developer Zone Articles

You can reply to any of the forum topics below by clicking on the title. Please do not include private information such as your email address or product serial number in your posts. If you need to share private information with an Intel employee, they can start a private thread for you.

New topic    Search within this forum     Subscribe to this forum


Intel MPI 3.2.2.006 and Supported OS and number of cores per machine
By Michael Charissis1
Has intel made a statement as to the last know good version of Red Hat that supports Intel MPI 3.2.2.006.  We have a new cluster with 20 cores/per node and have observed a fortran system call failing when more than 15 core per node are used.  This machine is running Red Hat 6.6 x86_64. Alternatively are their known conditions where Intel MPI 3.2.2.006 will fail.
Bug Report : MPI_IRECV invalid tag problem
By Xudong X.1
Hi, there, In MPI_5.0.3, the MPI_TAG_UB  is set to be 1681915906.  But internally, the  upper bound is  2^29 = 536870912, as tested out by the code attached. Same code will run just fine in MPI 4.0.3. Just to let you guys know the problem. Hope to see the fix soon. Thanks. Xudong Encl: 2-1. Source Code !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! program main implicit none include"mpif.h" real :: ibuf(10000) integer ,save  :: tag=2**29-1,ierr integer :: req(MPI_STATUS_SIZE,2) CALL MPI_INIT(ierr) write(*,*)"Tag_UB=", MPI_TAG_UB, TAG CALL MPI_IRECV(ibuf, 1000_4, MPI_REAL, 0, tag, MPI_COMM_WORLD, req(1,1), ierr) write(*,*)"Pass ..." tag = tag+1 write(*,*)"Tag_UB=", MPI_TAG_UB, TAG CALL MPI_IRECV(ibuf, 1000_4, MPI_REAL, 0, tag, MPI_COMM_WORLD, req(1,2), ierr) PAUSE end !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2-2. The screen output is as follows: Tag_UB=  1681915906   536870911  Pass ...  Tag_UB=  1681915906   536870912 Fatal error in ...
mpivars.sh to build path automatically
By Tiago M.10
Looks like on Linux the intel MPI runtime hardcodes the path of mpivars.sh, eg: I_MPI_ROOT=/opt/intel/impi/4.1.3.049; export I_MPI_ROOT On windows on the other hand the path is dynamically generated: SET I_MPI_ROOT=%~dp0..\.. Is there any reason to why the path cannot also be automatically generated on Linux? http://stackoverflow.com/questions/242538/unix-shell-script-find-out-whi... We have two situations were this would help: 1 - redistributing the mpi runtime with our application, and 2 - having machines with that folder mounted into different mount points.
License File Activation
By KK1
I just received my serial number of single user Intel Cluster Studio 2015 (Linux).  I had done product registration and generated a license file.  However, the license file generation page didn't show any information or steps of "how to apply the license file"... I am using an evaluation version of Intel Cluster Studio 2015 in Linux workstation.   So, I want to use the above license file.  I copy the license file into /opt/intel/license folder.  Do I need to execute any command?  Is there any guidelines or info. Thx.
MPI 5.0.2.044 Library Link Error
By dingjun.chencmgl.ca4
Hi, Everyone, Under Linux OS, I built my MPI application with Intel MPI 5.0.2.044.  There is no error in compiling but there are following error in linking MPI library. I am using the Intel MPI's  libmpifort.a and libmpi_mt.a for linking my application. LIBS          = -L/opt/intel/composer_xe_2013_sp1.2.144/mkl/lib/intel64 -lmkl_intel_lp64 \                 -lmkl_intel_thread -lmkl_core /net/rdnas/home/dingjun/intel/impi/5.0.2.044/intel64/lib/libmpi_mt.a /net/rdnas/home/dingjun/intel/impi/5.0.2.044/intel64/lib/libmpifort.a The following error occurred:   /net/rdnas/home/dingjun/intel/impi/5.0.2.044/intel64/lib/libmpi_mt.a(dapl_scan.o): In function `I_MPIC_coll_scan': /tmp/mpi5.xtmpdir.7b663e0dc22b2304e487307e376dc132.15926_32e/mpi5.32e.ww44.20141030/dev/x86_64/release_mt/../../src/mpid/ch3/channels/nemesis/netmod/dapl/coll/dapl_utils.h:758: undefined reference to `__I_MPI__intel_fast_memcpy' /net/rdnas/home/dingjun/intel/impi/5.0.2.044/intel64/lib/libmpi_mt.a(dapl_scatter.o): In...
Intel MPI
By Nicolay1
Hello. I am developing fault tolerant communicaction layer (MPI-like). So  this layer is slow now.  Can I learn something about internal Intel MPI architecture to understand basic principles of big data transfering over different networks. Can I also contact to developers of Intel MPI library to share experiences. Nicolay.
Intel MPI, DAPL and libdaplomcm
By Bryan C.13
Recently, we upgraded our system and have installed Mellanox OFED 2.2-1 in order to support native MPI calls between Xeon Phis.  Our system is a mixture of non-Phi nodes and Phi nodes. In the course of the upgrade, it seems that something has changed with regard to how Intel MPI (v4.1.3) determines which DAPL provider to utilize for jobs that do not specify a fabric, fabric list or provider.  And even when the DAPL fabric is chosen (I_MPI_FABRICS = shm:dapl), we're getting a message if a specific provider isn't selected.  We do not set any default fabrics or providers via our modules. The message is:  DAT: library load failure: libdaplomcm.so.2: cannot open shared object file: No such file or directory This is occurring on non-Phi nodes.  MPSS is only installed on Phi nodes, and thus, libdaplomcm is only on Phi nodes. According to the Intel MPI reference manual, IMPI will choose the first DAPL provider it finds, but the providers that involve libdaplomcm are all lower in the /etc/da...
Problem lauching mpiexec
By Olivier B.2
Hello, I do not succeed in lauching mpiexec. I'm working with Intel Fortran Compiler 11.1, and Intel parallel studio XE 2015, on windows 7. In fact I'm using mpiexec to launch a hydraulic simulation with TELEMAC software (http://www.opentelemac.org). This software uses for parallel simulation MPICH2. When I launch the command "mpiexec -n 4 xxx.exe", I'm asking to give my Account and my password. Is this password the password of the user of the computer? Or is it a password given by Intel with the installation? Sorry my question is maybe not clear, but I'm a beginner in this field. Olivier
Subscribe to Forums
  • What are some key things I can learn about my program using Intel® Trace Analyzer and Collector?
  • The Intel Trace Analyzer and Collector is a graphical tool used primarily for MPI-based programs. It helps you understand your application's behavior across its full runtime. It can help find temporal dependencies in your code and communication bottlenecks across the MPI ranks. It also checks the correctness of your application and points you to potential programming errors, buffer overlaps, and deadlocks.

  • Will Intel Trace Analyzer and Collector only work with Intel MPI Library?
  • No, the Intel Trace Analyzer and Collector support all major MPICH2-based implementations. If you're wondering whether your MPI library can be profiled using the Intel Trace Analyzer and Collector, you can run a simple ABI-compatibility check by compiling the provided mpiconstants.c file and verifying the values with the ones provided in the Intel Trace Collector Reference Guide..

  • Can Intel Trace Analyzer and Collector be used on applications for Intel® Many Integrated Core Architecture (Intel® MIC Architecture)?
  • Yes, Intel MIC Architecture is fully supported by the Intel Trace Analyzer and Collector.

  • What file and directory permissions are required to use Intel Trace Analyzer and Collector?
  • You do not need to install special drivers, kernels, or acquire extra permissions. Simply install the Intel Trace Analyzer and Collector in the $HOME directory and link it with your application of choice from there.

  • Should I recompile/relink my application to collect information?
  • It depends on your application. For Windows* OS, you have to relink your application by using the –trace link-time flag.

    For Linux* OS (and if your application is dynamically linked), you do not need to relink or recompile. Simply use the –trace option at runtime (for example: mpirun –trace).

  • How do I control which part of my application should be profiled?
  • The Intel Trace Collector provides several options to control the data collection. By default, only information about MPI calls is collected. If you'd like to filter which MPI calls should be traced, create a configuration file and set the VT_CONFIG environment variable.

    If you'd like to expand the information collected beyond MPI and include all user-level routines, recompile your application with the –tcollect switch available as part of the Intel® Compilers. In this case, Intel Trace Collector will gather information about all routines in the application, not just MPI. You can similarly filter this via the –tcollect-filter compiler option.

    If you'd like to be explicit about which parts of the code should be profiled, use the Intel Trace Collector API calls. You can manually turn tracing on and off via a quick API call.

    For more Information on all of these methods, refer to the Intel Trace Collector Reference Guide..

  • What file format is the trace data collected in?
  • Intel Trace Collector stores all collected data in Structured Tracefile Format (STF) which allows for better scalability across both time and processes. For more details, refer to the "Structured Tracefile Format" section of Intel Trace Collector Reference Guide.

  • Can I import or export trace data to/from Intel Trace Analyzer and Collector?
  • Yes, you can export the data from any of the Profile charts (Function Profile, Message Profile, and Collective Operations Profile) as part of the Intel Trace Analyzer interface. To do this, open one of these profiles in the GUI, right-click to bring up the Context Menu, and select the "Export Data" option. The data will be saved in simple text format for easy reading.

    At a separate level, you can save your current working Intel Trace Analyzer environment via the Project Menu. If you choose to "Save Project", your current open trace view and associated charts will be recorded as they are open on your screen. You can later choose to "Load Project" from this same menu, which will bring up a previously-saved session.

  • What size MPI application can I analyze with Intel Trace Analyzer and Collector?
  • It depends on how large or complex your application is, how many MPI calls you are making, and for how long you are running. There are no internal limitations on the size of the MPI job but there are plenty of external ones. It all depends on how much memory is available on the system (per core) both for the application, the MPI library, and for the Intel Trace Collector processes, as well as disk space availability. Any additional flags enabled (for example, storing call stack and source code locations) cause an increase in the size of the trace file. Filtering out unimportant information is always a good solution to reducing trace files.

  • How can I control the amount of data collected to a reasonable amount? What is a reasonable amount?
  • Each application is different in terms of the profiling data it can provide. The longer an application runs, and the more MPI calls it makes, the larger the STF files will be. You can filter some of the unnecessary information out by applying appropriate filters (see Question #6 for more details or check out some tips on Intel Trace Collector Filtering).

    Additionally, you can be restricted by the resources allocated to your account; consult your cluster administration about quotas and recommendations.

  • How can I analyze the collected information?
  • Once you have collected the trace data, you can analyze it via the Graphical Interface called the Intel Trace Analyzer. Simply call the command ($ traceanalyzer) or double-click on the Intel Trace Analyzer icon and navigate to your STF files via the File Menu.

    You can get started by opening up the Event Timeline chart (under the Charts Menu) and zooming in at an appropriate level.

    Check out the Detecting and Removing Unnecessary Serialization Tutorial on ideas how to get started. For details on all Intel Trace Analyzer functionality, refer to the Intel Trace Analyzer Reference Guide.

  • Can I use Intel Trace Analyzer and Collector with Intel® VTune™ Amplifier XE, Intel® Inspector XE, or other analysis tools?
  • While these tools would collect information separate from each other, in their own format, it's easy enough to use the Intel VTune Amplifier XE and Intel Inspector XE tools under an MPI environment. Check each tool's respective User's Guide for more info on Viewing Collected MPI Data.

    You can use tools such as Intel VTune Amplifier XE and Intel Inspector XE for node-level analysis, and use the Intel Trace Analyzer and Collector for cluster-level analysis.

Intel® Trace Analyzer & Collector

Getting Started?

Click the Learn tab for guides and links that will quickly get you started.

Get Help or Advice

Search Support Articles
Forums - The best place for timely answers from our technical experts and your peers. Use it even for bug reports.
Support - For secure, web-based, engineer-to-engineer support, visit our Intel® Premier Support web site. Intel Premier Support registration is required.
Download, Registration and Licensing Help - Specific help for download, registration, and licensing questions.

Resources

Release Notes - View Release Notes online!
Intel® Trace Analyzer and Collector Product Documentation - View documentation online!
Documentation for other software products