Optimize Serial and Parallel Performance
Intel® VTune™ Amplifier XE 2013 is the premier performance profiler for C, C++, C#, Fortran, Assembly and Java*.
![]() Functions using the most CPU time float to the top of the list. Click on a function to see the call stack. Double click to see the source with detailed profile data. |
Easy
Performance optimization can be difficult, but the performance profiling tool you use shouldn’t be.
Versatile – Rich Set of Performance Profiles
Whether you are tuning for the first time or doing advanced performance optimization, VTune Amplifier XE 2013 provides the data needed to meet a wide variety of tuning needs. Collect a rich set of performance data for hotspots, threading, locks & waits, DirectX*, bandwidth and more.
Productive – Sort, Filter and Visualize
Good data is not enough. You need tools to mine the data and make it easy to understand. Powerful analysis lets you sort, filter and visualize results on the timeline and on your source.
New for 2013!
Call counts, hardware stack sampling, better bandwidth analysis, Java profiling, tune Intel® Xeon Phi™ products, user tasks, DirectX* frames, power analysis and more.
Quotes
“The new VTune™ Amplifier XE brings even more capability to an already indispensable tool. The sampling based call stack hotspots is excellent and alone is worthy of the upgrade. We have also been impressed by how the concurrency and Locks and Waits analysis can even provide useful data on complex applications such as Premiere Pro.”
Rich Gerber - Engineering Manager, MediaCore, Adobe Systems Inc.
“The new interface is a joy to use. Intel® VTune Amplifier XE gives us precise, down-to-the-metal performance data that’s invaluable for pinpointing hotspots and evaluating the effect of optimizations”
Daniel Schwarz, Performance Engineer, Nik Software
“Intel® VTune™ Amplifier XE’s timeline is very information intensive. It organizes the data I need to tune threaded applications.”
Sergey Zaritchny, Software Development Manager, Open Cascade SAS
“Last week, Intel® VTune™ Amplifier XE helped us find almost 3X performance improvement. This week it helped us improve the performance another 3X.”
Claire Cates, Principal Developer, SAS Institute Inc.
“One of Intel® VTune™ Amplifier XE’s best features is that it is easy to use. I did not need to read the documentation.”
Richard Shepherd, Software Engineer, ESRI (UK) Limited
Quickly Locate Code Taking A Lot of CPU TimeHotspots analysis gives you a sorted list of the functions using a lot of CPU time. Click [+] for the call stacks. Double click to see the source. |
|
See the Results on Your SourceA double click from the function list takes you to the hottest spot in the function. |
|
Tune Threading with Locks and Waits AnalysisQuickly find a common cause of slow performance in parallel programs: waiting too long on a lock while the cores are underutilized during the wait. Profiles like hotspots and locks & waits use a software collector that works on both Intel and compatible processors. |
|
Mine the Data with Timeline FilteringSelect a time range in the timeline to filter out data (e.g., application startup) that masks the information you need. When you select and filter in the timeline, the grid that lists functions using a lot of CPU time updates to show the list filtered for the selected time. |
|
![]() |
Visualize Thread BehaviorSee when threads are running and waiting, and when transitions occur. Balance workloads. |
Profile a Running ApplicationThere is no need to stop and re-launch the application when profiling
|
|
Low Overhead / High Resolution Hardware ProfilingIn addition to hotspots analysis that works on both Intel and compatible processors, VTune Amplifier XE 2013 has lightweight hotspots analysis that uses the Performance Monitoring Unit (PMU) on Intel processors to collect data with very low overhead. Increased resolution (~1 ms vs. ~10 ms) can find hot spots in small functions that run quickly. |
|
Advanced Analysis Like BandwidthPreset profiles provide an easy “point and shoot” set-up. Choose Hotspot, Lightweight Hotspot, Concurrency, Locks and Waits or more advanced analyses. No memorizing complex event names. Advanced profiles like memory bandwidth analysis, memory access and branch mispredictions find tuning opportunities. |
|
Opportunities HighlightedThe cell is highlighted in pink when there is a potential tuning opportunity. Hover to get suggestions. |
|
No special buildsUse a production build with symbols from your normal compiler. |
Low overheadAccurate results you can count on. |
Command lineAutomate regression analysis. Simple remote collection. |
System Wide AnalysisTune drivers, kernel modules and multi-process apps. |
|
|
|
Intel® Threading Building BlocksBuilt-in understanding of parallel programming models means profiling data is described using familiar terms from the source, not with cryptic internal runtime labels. |
|
|
|
|
|
|
|
Technical SpecificationsFor additional details, please see the release notes. |
Low Overhead / High Resolution Hardware ProfilingIn addition to hotspots analysis that works on both Intel and compatible processors, VTune Amplifier XE 2013 has lightweight hotspots analysis that uses the Performance Monitoring Unit (PMU) on Intel processors to collect data with very low overhead. Increased resolution (~1 ms vs. ~10 ms) can find hot spots in small functions that run quickly. |
|
Advanced Analysis Like BandwidthPreset profiles provide an easy “point and shoot” set-up. Choose Hotspot, Lightweight Hotspot, Concurrency, Locks and Waits or more advanced analyses. No memorizing complex event names. Advanced profiles like memory bandwidth analysis, memory access and branch mispredictions find tuning opportunities. |
|
|
|
|
|
|
|
|
|
|
|
No special buildsUse a production build with symbols from your normal compiler. |
Low overheadAccurate results you can count on. |
Command lineAutomate regression analysis. Simple remote collection. |
Videos to help you get started.
![]()
- Introduction

- Series 1

- Series 2

- Series 3

- Series 4

- Series 5

Previously recorded Webinars:
- Performance analysis on Intel® Xeon® Phi™ Coprocessor

- How Intel® Parallel Studio XE is used to improve the HMMER application
- Webinar name 3

- Webinar name 4

- Webinar name 5

- Webinar name 6

More Tech Articles
8:44 PM PDT
1:36 PM PDT
10:13 AM PDT
3:39 PM PDT
Pages
Product Documentation and Tutorials
- For Windows*
-
Loading Intel Software Documentation...
- For Linux*
-
Loading Intel Software Documentation...
Supplemental Documentation
3:51 PM PST
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
Pages
- What is the difference between hotspots and lightweight hotspots?
-
Hotspots Lightweight Hotspots Uses the software collector Uses the hardware collector and the on chip Performance Monitoring Unit (PMU) No driver required Requires a driver Runs on Intel® and compatible processors Requires a genuine Intel® processor for collection ~10ms resolution ~1ms resolution (finds smaller functions) Collects call stacks to show calling sequences
Optional call stack collectionWorks in virtual environments Works in a virtual environment only when supported by the VM vendor (e.g., vSphere* 5.1)
- Can I install and use Intel VTune Amplifier XE on a system with a compatible processor not manufactured by Intel® Corporation?
-
Yes. Intel VTune Amplifier XE will operate on both Intel® processors and compatible processors when analyzing applications containing Intel® instructions. Profiling features that use the software collectors work on both Intel processors and compatible processors. Profiling features that use the hardware collectors and the on-chip performance monitoring unit require a genuine Intel processor for data collection, but after collection the results can analyzed on a compatible processor.
- Can I run a performance analysis on a remote system?
-
Yes.
- Do I need multiple licenses to do remote data collections?
-
No, you do not need additional licenses for remote collection as long as the remote machine is the same OS (Linux or Windows*) as your license. Once you have the product, the CLI installer (command line installer) is part of it and can be installed on any number of systems. You can collect the data on the remote system, but you will need a license to view the data. Copy the results directory to a system with the full product installed for viewing. For more details see “Remote Tuning Workflow ” in the documentation. For installation details see “Installing Collectors on Remote Systems” in the release notes.
- Do I need to recompile?
-
No, you do not need to recompile in order to profile with Intel® VTune Amplifier XE. However, it is recommended that you have debug and symbol information available for your optimized application in order to get the most complete and useful results. Thus, your release build process may need to be modified to add symbol information to the optimized build.
- Do I need to use the Intel compiler to use Intel® VTune Amplifier XE?
-
No, you do not need the Intel compiler to analyze applications. However, if you are using OpenMP, it is recommended that you use the Intel runtime if possible to get the best results.
- Why can’t I see my source code?
-
There are several possible reasons why VTune Amplifier XE may be unable to see your source.
In order for source code to be visible you need to compile your code so that debug information is available. For example, on Linux*, verify you are compiling with the “-g” flag.
You also need to let VTune Amplifier XE know where your source files, binary files and symbol files are located. To do this, open or create a Project and click on the “Project Properties” button. In the Project properties dialog, click on the “Search Directories” tab. In the pull down menu, click on “All files” and then specify the directory where your files exist. If you have any subdirectories remember to check the “Search subdirectories” box.
- Do I need to be root to run the hardware collector used with Lightweight Hotspots and Advanced Analysis?
-
No. On Linux*, you need to be root to install the driver for the hardware collector, but once it is installed root access is not required. On Linux*, you do need to be a member of the driver access group (“vtune ” by default) to use the hardware collector. The hardware collector is used for lightweight hotspots analysis and advanced analysis. For more information see “Installing the Sampling Driver ” in the documentation.
- What file and directory permissions are required to use VTune™ Amplifier XE?
-
Because the hardware-based sampling analysis types require communication with the Performance Monitoring Unit (PMU) of the central processor, the installer attempts to install a device driver. For Windows*, the driver is signed and the person installing must be part of the Administrators group. On Linux*, the person installing the software must be root or have sudo access to install the driver. However, a Linux user can install the software locally without the device driver and still use the user-mode sampling analysis types: Hotspots, Concurrency, and Locks-and-Waits. If the user is able to install the software as ‘root’, any user that desires to collect hardware-based samples must be part of the user group defined during the install. By default, this is the ‘vtune’ group, but it can be changed by accessing the Advanced options of the installer (install.sh).
- Why can’t I import results?
-
In order to import results into VTune Amplifier XE, you must first create a project to contain the imported results. In the VTune Amplifier XE, click on the File->New->Project menu. This will bring up a dialog asking you to select a project name. Enter a name and press “OK”. VTune Amplifier XE will display the “Project Properties” dialog. If you are only importing results into the project then you will not need to specify an application name. However, if you want to view source of the imported results, you need to specify the search directories where your source and binaries are located. In the Project properties dialog, click on the “Search Directories” tab. In the pull down menu, click on “All files” and then specify the directory where your files exist. If you have any subdirectories remember to check the “Search subdirectories” box.
- I added a path to the Search Directories, but nothing changed?
-
The Search Directories are used during finalization and that normally occurs after data collection completes. In order for new “Search directory” paths to take affect VTune Amplifier XE must re-resolve your results with the new information provided. Click on the “Analysis Type” tab and then press the “Re-resolve” button on the far right, located directly below the “Start” and “Project Properties” buttons.
- Why do the sample counts look wrong?
-
Sometimes, the sample counts may be displayed on source lines that are not normally associated with executable code, for example, the closing brace of a ‘for’ or ‘while’ loop. This may appear to be an error but is a result of the instructions generated by the compiler. Viewing the assembly code can reveal that the debug information for the assembly instructions to which the samples are attributed, are tagged as belonging to that source line, i.e., the closing brace.
Other times, viewing of the assembly instructions may show that certain hardware events were collected on instructions that could not possibility generate that event, e.g., a memory event on a jump instruction or an arithmetic event on a memory instruction. This is known as “event skid” and is a result of the processor being unable to stop the execution of some micro-ops before sampling the instruction pointer. Thus, the IP is pointing at a subsequent instruction by the time the sample is taken. Typically, you can determine which instruction was responsible for the event by examining the instruction flow.
- How can I use Intel® VTune Amplifier XE to see how much time is spent doing Disk I/O?
-
If your application is doing blocking I/O, the function call attributed to the file accesses should appear in Hotspots Analysis. Additionally, if you have multiple threads waiting to access a single file, the synchronization object protecting the file , e.g. a Critical Section, should show up in the Locks and Waits analysis.
Intel® VTune™ Amplifier XE 2013
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® VTune™ Amplifier XE 2013 documentation
Documentation for other software products
Featured Support Topics
Pages
OS Support
Windows*
Linux*
Languages
C, C++, C#, Fortran, Java and Assembly
Related Content
Documentation
Product Brief
Release Notes
Case Studies
Forums
Blogs
Events
Learning Lab
Software EULA
Intel GPA
Intel VTune Amplifier XE is included in these suites:
Intel® Parallel Studio XE
Intel® C++ Studio XE
Intel® Fortran Studio XE
Intel® Cluster Studio XE
Intel® System Studio (incl. Intel VTune Amplifier for Systems)













