Visible to Intel only — GUID: GUID-4DA4C500-9978-491B-AE19-3B7BACE9136F
Visible to Intel only — GUID: GUID-4DA4C500-9978-491B-AE19-3B7BACE9136F
Tutorials and Samples
Intel® VTune™ Profiler provides web tutorials using sample code for step-by-step instructions on configuring and interpreting performance analysis.
Analyze Common Performance Bottlenecks - C++ Sample Code
Sample: pre-built matrix C++ matrix multiplication application. The pre-built application is available from the Project Navigator when you first launch Intel VTune Profiler. You can access the sample code from:
Linux: <install-dir>/samples/en/C++/matrix
Windows: <install-dir>\samples\en\C++\matrix
Learning Objective:
Demonstrates: Iterative application optimization with VTune Profiler, finding algorithmic and hardware utilization bottlenecks
Performance issues: memory access, vectorization
Analyses used: Performance Snapshot, Hotspots, Memory Access, HPC Performance Characterization, Microarchitecture Exploration
Analyzing an OpenMP* and MPI Application - C++ Sample Code
Linux* Tutorial: HTML
Sample: heart_demo C++ application that simulates electrophysiological heart activity. You can access the sample code at https://github.com/CardiacDemo/Cardiac_demo.
Learning Objective:
Demonstrates: Identifying issues in a hybrid OpenMP and MPI application.
Analysis/tools used: Application Performance Snapshot (APS), Intel Trace Analyzer and Collector, and VTune Profiler's HPC Performance Characterization analysis
Performance Analysis Cookbook
For end-to-end tuning and configuration use cases, explore the VTune Profiler Performance Analysis Cookbook that introduces such recipes as:
Tuning Recipes:
Configuration Recipes:
See more recipes here.
To install and set up the VTune Profiler sample code:
Copy the archive file from the installation directory to a writable directory or share on your system.
Extract the sample from the archive.
Samples are non-deterministic. Your screens may vary from the screen shots shown throughout these tutorials.
Samples are designed only to illustrate the VTune Profiler features and do not represent best practices for tuning any particular code. Results may vary depending on the nature of the analysis and the code to which it is applied.