Intel Trace Analyzer and Collector 7.2.011 | 65,9 MB The Intel Trace Collector is a low-overhead tracing library that performs event-based tracing in applications. You can analyze the collected trace data for performance hotspots and bottlenecks. The product is completely thread safe and integrates with C/C, FORTRAN and multi-threaded processes with and without MPI. It supports binary instrumentation and fail-safe mode. Additionally it can check for MPI programming and system errors.
Why Intel Trace Analyzer and Collector 7.1?
Analyze MPI performance. Speed up parallel application runs. Locate hotspots and bottlenecks. Compare trace files with graphics providing extensively detailed analysis and aligned timelines.
* Supported on Linux* and Microsoft* Windows* (Windows Compute Cluster Server* 2003, Windows XP and Windows Server* 2003)
* Intuitive full color customizable GUI with many drill down view options
* Highly scalable with low overhead and efficient memory usage
* Easy run-time loading - or instrument an MPI application executable
* MPI Correctness Checking Library detects many types of errors in communication
* Integrated online help
* Easy installation and full documentation
* Full tracing and/or light-weight statistics gathering
Many features, many options, major performance improvements.
* PIN-based binary instrumentation
* Runtime behavior displayed by function, process, thread, timelines or cluster or node
* Multiple types of filtering (functions, processes, messages) and aggregation
* Performance counter data recording can be displayed as timeline
* Trace data is cached to reduce runtime overhead and memory consumption
* Traces multi-threaded MPI applications for event-based tracing to non-MPI applications
* Fail safe tracing
* Support for MPI-1, SHMEM, MPI-IO, ROMIO
* Distributed memory checking with the MPI Correctness checking library
Trace Collector
* Automated MPI tracing and MPI Correctness Checking
* Generic distributed (non-MPI) and single process tracing
* Thread level tracing with traces created even if the application crashes
* HPM data collection (PAPI, rusage, OS-counters)
* Configurable tracefile parameters
* Feature disabling/enabling
* Tuning parameters
* Distributed Memory checking with Valgrind*
* Binary runtime instrumentation
* Compiler instrumentation
o Icc/ifort/icpc -tcollect
o Gcc/g++ -finstrument-functions
* API: source code instrumentation (counter, function, message and collective operation logging)