This section describes the Intel® Trace Collector functionality and provides instructions on how to use its features. See the brief overview of each sub-section in the table below.
|Tracing MPI Applications||General instructions on how to trace various types of MPI applications.|
|Tracing MPI Load Imbalance (Linux* OS)||Information on tracing MPI events that cause application load imbalance.|
|Tracing User Defined Events||Information on tracing non-MPI user-defined events in MPI applications. You can do this automatically for all application functions, or manually only for selected functions or code regions.|
|Configuring Intel® Trace Collector||Information on how to configure various aspects of Intel® Trace Collector behavior. Configuration is used to enable and disable some Intel Trace Collector functionality and for filtering trace data.|
|Filtering Trace Data||Description of the filtering capabilities of Intel® Trace Collector. Use filtering to trace only information of interest reducing the trace file size and making the results easier to analyze.|
|Recording OpenMP* Regions Information||Instructions on recording the information about the OpenMP* regions in your application into the trace file.|
|Tracing System Calls (Linux* OS)||Information on tracing system input/output calls.|
|Collecting Lightweight Statistics||Information on collecting the lightweight statistics about function calls and their communication. Collecting the lightweight statistics is useful for understanding an unknown application.|
|Recording Source Location Information||Instructions on recording the locations of certain functions in the source code. This enables you to easily navigate the source files when analyzing the trace data.|
|Recording Hardware Performance Information (Linux* OS)||Information on recording the PAPI hardware performance counters.|
|Recording Operating System Counters||Information on recording operating system counters, which provide useful information about nodes.|
|Tracing Library Calls||A use case of tracing particular data using various Intel® Trace Collector capabilities. In the example provided, an instrumented application with the use of external libraries is used. Data tracing is presented from the points of view of the application developer and the library developers.|
|Correctness Checking||Information on the correctness checking capability. The correctness checker can detect deadlocks, data corruption, and errors with MPI parameters, data types, buffers, communicators, point-to-point messages and collective operations.|
|Tracing Distributed Non-MPI Applications||Information on tracing distributed applications that work without MPI.|
For more complete information about compiler optimizations, see our Optimization Notice.