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:

  • Fast, light weight, scalable MPI performance analysis
  • 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

Featured Articles

Aucun contenu trouvé

More Tech Articles

Aucun contenu trouvé
S’abonner à Articles de la Zone des développeurs Intel

Supplemental Documentation

Aucun contenu trouvé
S’abonner à Articles de la Zone des développeurs Intel

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


MPI_Init_thread or MPI_Init failed in child process
Par Yongjun L.7
I have two programs, A and B. They all are developed with MPI. A will call B.  If I directly start A and call B, every thing is OK. If I start A with mpiexec, like mpiexec -localonly 2 A.exe, and call B. MPI_Init_thread or MPI_Init will fail in B.  Below is the error message I got. [01:2668]..ERROR:Error while connecting to host, No connection could be made because the target machine actively refused it. (10061) [01:2668]..ERROR:Connect on sock (host=localhost, port=53649) failed, exhaused all end points SMPDU_Sock_post_connect failed. [1] PMI_ConnectToHost failed: unable to post a connect to localhost:53649, error: Undefined dynamic error code uPMI_ConnectToHost returning PMI_FAIL [1] PMI_Init failed. Fatal error in PMPI_Init_thread: Other MPI error, error stack: MPIR_Init_thread(659): MPID_Init(154).......: channel initialization failed MPID_Init(448).......: PMI_Init returned -1 Can anyone tell me what is the problem? How to solve it? Thanks Yongjun
need to type "Enter" ?
Par dingjun.chencmgl.ca1
Hi, Everyone, I am running my hybrid MPI/OpenMP jobs on 3-nodes Infiniband PCs Linux cluster. each node has one MPI process that has 15 OpenMP threads. This means my job runs with 3 MPI processes and each MPI process has 15 threads. the hosts.txt file is given as follows: coflowrhc4-5:1 coflowrhc4-6:1 coflowrhc4-7:1  I wrote the following batch file as follows: /************** batch file******************/ export CMG_LIC_HOST=rlmserv export exe=/cmg/dingjun/imexLocal/imex_xsamg_dave.exe export LD_LIBRARY_PATH=/cmg/dingjun/imexLocal/linux_x64/lib export OMP_SCHEDULE=static,1 export KMP_AFFINITY=compact,0 export datadir=/cmg/dingjun/imexdatasets/7testproblems/mx1041_rb cd /cmg/dingjun/imexdatasets/7testproblems/mx1041_rb mpirun -machinefile hosts.txt ${exe} -fgmres -f ${datadir}/mx1041x105x10loa2_rb_xsamg.dat -log -jacdoms 16 -parasol 16 -o mx1041x105x10loa2_rb_xsamg_3MPI15threads_run7 export datadir=/cmg/dingjun/imexdatasets/7testproblems/mx521_rb cd /cmg/dingjun/imexdataset...
Intel MPI 5.0.3.048 and I_MPI_EXTRA_FILESYSTEM: How to tell it's on?
Par thematt3
All, I hope the Intel MPI experts here can help me out. Intel MPI 5.0.3.048 was recently installed on our cluster, a cluster that uses a GPFS filesystem. Looking at the release notes I saw that "I_MPI_EXTRA_FILESYSTEM_LIST gpfs" was now available. Great! I thought I'd try to see if I can see an effect or not. However, I'm having trouble detecting whether it's on or not. I tried running a simple Hello World (no I/O, but simple) with I_MPI_DEBUG=9. When I do so, I get the usual splat of information but if I pass in "-genv I_MPI_EXTRA_FILESYSTEM on -genv I_MPI_EXTRA_FILESYSTEM_LIST gpfs" or not, I never see anything in the I_MPI_DEBUG output that says if I enabled it or not. I even tried I_MPI_DEBUG=100, but nothing. Is there a way to know if this has been enabled? I was hoping to try to figure out an MPI-I/O benchmark that would let me see a difference, but if I can't tell if Intel MPI is actually enabling it, I'm a bit wary to thrash my disks without being sure. Thanks, Matt
Cannot use jemalloc with IntelMPI
Par Eloi Gaudry3
Hi, I've tried to bench several memory allocators on Linux (64-bit) such as ptmalloc2, tcmalloc and jemalloc with an application linked against IntelMPI (4.1.3.049). Launching any application linked with jemalloc will cause the execution to abort with a signal 11. But the same application, when not linked with IntelMPI will work without any issue. Is IntelMPI doing its own malloc/free ? How can this issue be overcome ? Thanks, Eloi  
How many processes we can run run HPL on with Intel MPI ?
Par Nihir Parikh6
If we are using evaluation version of Intel MPI/compiler/MKL (cluster tools) how many cores/processes we can run HPL on?
problem when multiple MPI versions installed
Par tangzhanghong98@yahoo.com8
Dear all, I have a problem to launch processes when multiple MPI versions installed. The processes work before I installed latest MPI 5.0.3.048: C:\Program Files (x86)\Intel\MPI\4.1.3.047>mpiexec -wdir "Z:\test" -mapall -hosts 10 n01 6 n02 6 n03 6 n04 6 n05 6 n06 6 n07 6 n08 6 n09 6 n10 6 Z:\test However, after I installed MPI 5.0.3.048, the following errors displayed when I launch mpiexec in the environment of 4.1.3.047: Aborting: unable to connect to N01, smpd version mismatch   I have already run the following command in the environment of 5.0.3.048 before launching mpiexec: hydra_service -stop   Could anyone help me to take a look at it? Is it possible to let both versions work in the cluster?   Thanks, Zhanghong Tang  
Intel MPI 3.2.2.006 and Supported OS and number of cores per machine
Par 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
Par Xudong X.2
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 ...
S’abonner à 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

Featured Support Topics

Aucun contenu trouvé