Intel VTune Amplifier XE 2013 is the serial / threaded profiler for programs written in C, C++, C#, Fortran, Assembly and Java*.
Please contact NSC Support if you have any questions or problems.
To access all the features of VTune on triolith you must be a member of the “VTune” group: request membership by writing to NSC Support. To use VTune on a compute node with all features (which require a kernel module to be loaded), request the “constraint” vtune, e.g:
interactive --reservation=devel -N1 --exclusive --constraint=vtune -t 00:10:00
When the interactive session starts, load the vtune module and start vtune gui, e.g:
module add vtune/2013.u2 amplxe-gui
Note: VTune requires a whole (non-shared) node, so make sure you use “–exclusive”.
Note: if you leave out “–constraint=vtune” VTune will still work, but not all features will work properly. This is also what happens if you run VTune on a login node.
Compile the source code using either Intel or GNU compilers. Following flags are important:
-g : VTune uses the symbols to associate addresses to source lines. -O2 : it is highly recommended to compile the code with this flag. -shared-intel : for intel compiler, for user mode sampling and tracing analysis
VTune analysis can be run either in the command line mode or gui mode.
Run the program binary called exe as:
amplxe-cl <action> [action-option] [global-option] [[--] exe [exe-options]]
This example runs the Hotspots analysis for the target called exe, saves the analysis result in the r001hs subdirectory of the current directory, and displays the default summary report.
$ amplxe-cl -collect hotspots -result-dir r001hs ./exe where: -collect is an action; hotspots is an argument of the action -result-dir is an action-option; r001hs is an argument of the action-option
To see all available actions, enter amplxe-cl -help
For visualizing the results
$ amplexe-gui results-folder
To use the VTune in the GUI mode use:
$ amplexe-gui once the gui starts create a new project. As the new project is created it will ask for binary name, path and binary parameters, if any. Then start the analysis