- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -
- Information contained in the HLRS Wiki is not legally binding and HLRS is not responsible for any damages that might result from its use -

VTune: Difference between revisions

From HLRS Platforms
Jump to navigationJump to search
No edit summary
No edit summary
Line 20: Line 20:


=== Using Intel VTune ===
=== Using Intel VTune ===
To perform the performance analyse of your application with VTune you don’t need special compiler wrapper or libraries. Just recompile and relink your code with extra –g option in order to include debug information. VTune works well for dynamically linked binaries. [https://software.intel.com/content/www/us/en/develop/documentation/vtune-help/top/set-up-analysis-target/linux-targets/analyzing-statically-linked-binaries-on-linux-targets.html Here] you can find some tips for statically linked binaries
To perform the performance analyse of your application with VTune you don’t need special compiler wrapper or libraries. Just recompile and relink your code with extra –g option in order to include debug information. VTune works well for dynamically linked binaries. [https://software.intel.com/content/www/us/en/develop/documentation/vtune-help/top/set-up-analysis-target/linux-targets/analyzing-statically-linked-binaries-on-linux-targets.html Here] you can find some tips for statically linked binaries.
 
Example:
Example:
<pre>
<pre>
module load compiler/intel
module load vtune # set up VTune environment  
module load performance/vtune # set up VTune environment
module load gcc mpt
module load mpi/impi          # if MPI needed
</pre>
</pre>


Compilation example:  
Compilation example:  
<pre>
<pre>
ifort -g -O2 prog.f90
mpicxx –O2 -g -Wl,-Bdynamic main.cpp
</pre>
</pre>


Analyzing MPI applications:
Run analysis:
VTune has both a GUI and command line tool: vtune-gui and vtune.
The following types of analysis are available on Hawk:
* ''hotspots'' - Analyze application flow and identify sections of code that take a long time to execute (hotspots).
* ''threading'' - Discover how well your application is using parallelism to take advantage of all available CPUs. Identify and locate synchronization issues causing overhead or idle wait time resulting in lost performance.
* ''memory-consumption'' - Analyze memory consumption by your Linux application, its distinct memory objects and their allocation stacks.
 
'''NOTE:''' ''The VTune project working directory and the results directory must be placed on lustre FS.''
Example:
<pre>
<pre>
mpirun –n4 amplxe-cl -c hotspots –r my_result -- path_to_my_app
module load vtune
module load gcc mpt
WORKDIR=/your/project/dir/on/lustre
cd ${WORKDIR}
mpirun -np 128  vtune -collect hotspots -r ${WORKDIR}/results_dir -- ./a.out your_input.file
</pre>
</pre>


=== Using Intel VTune on Cray machines ===
Report:
 
You can also generate the report in text form using the VTune command line tool:
Load the necessary module. For example:
<pre>
<pre>
module swap PrgEnv-cray PrgEnv-intel # set up MPI environment too
vtune -help report
module load performance/vtune        # set up VTune environment
vtune -report ''summary'' -r ${WORKDIR}/results_dir
</pre>
</pre>
Or you can open the results of analysis in vtune-gui tool.


Compilation example:  
For some use cases you might need to limit the amount of raw data to be collected. Define this limit in MB through the data-limit option:
<pre>
<pre>
ftn -dynamic -g -O2 prog.f90
mpirun -np 128 vtune -collect hotspots -data-limit=200 -- ./a.out
</pre>
</pre>


Analyzing MPI applications:
Some more information about VTune you can find here.
<pre>
aprun –n4 amplxe-cl -c hotspots –r myResult-@@@{at} -- path_to_my_app
</pre>


== See also ==
== See also ==
Line 60: Line 69:


== External links ==
== External links ==
* [http://software.intel.com/en-us/intel-vtune/ Intel® VTune™ Amplifier XE homepage]
* [https://software.intel.com/content/www/us/en/develop/tools/oneapi/components/vtune-profiler.html Intel® VTune™ Profiler homepage]
 
* [https://software.intel.com/content/www/us/en/develop/documentation/vtune-help/top/introduction.html Introduction to Intel® VTune™ Profiler]
[[Category:Performance Analyzer]]
[[Category:Performance Analyzer]]

Revision as of 16:25, 4 June 2021

Intel® VTune™ Profiler is a performance analysis tool for serial and multithreaded applications. Use VTune Profiler:
  • to determine the most time-consuming (hot) functions in your application
  • to discover on very fine-grained level which section of code (loop, source code line or even data field) do not effectively utilize available processor time
  • to analyse communication behavior that affects threaded performance
  • for accurate analysis with low overhead
  • for serial and multithreaded applications
    • MPI (MPT, OpenMPI)
    • OpenMP, Intel® oneAPI Threading Building Blocks, native threads
  • Languages:
    • C/C++/C#, Fortran, Python and others
Intel-logo.png
Developer: Intel
Platforms: Hawk, Vulcan
Category: Performance Analyzer
License: Commercial
Website: Intel® VTune™ Profiler homepage


Using Intel VTune

To perform the performance analyse of your application with VTune you don’t need special compiler wrapper or libraries. Just recompile and relink your code with extra –g option in order to include debug information. VTune works well for dynamically linked binaries. Here you can find some tips for statically linked binaries.

Example:

module load vtune # set up VTune environment 
module load gcc mpt 

Compilation example:

mpicxx –O2 -g -Wl,-Bdynamic main.cpp 

Run analysis: VTune has both a GUI and command line tool: vtune-gui and vtune. The following types of analysis are available on Hawk:

  • hotspots - Analyze application flow and identify sections of code that take a long time to execute (hotspots).
  • threading - Discover how well your application is using parallelism to take advantage of all available CPUs. Identify and locate synchronization issues causing overhead or idle wait time resulting in lost performance.
  • memory-consumption - Analyze memory consumption by your Linux application, its distinct memory objects and their allocation stacks.

NOTE: The VTune project working directory and the results directory must be placed on lustre FS. Example:

module load vtune
module load gcc mpt
WORKDIR=/your/project/dir/on/lustre
cd ${WORKDIR}
mpirun -np 128  vtune -collect hotspots -r ${WORKDIR}/results_dir -- ./a.out your_input.file

Report: You can also generate the report in text form using the VTune command line tool:

vtune -help report 
vtune -report ''summary'' -r ${WORKDIR}/results_dir

Or you can open the results of analysis in vtune-gui tool.

For some use cases you might need to limit the amount of raw data to be collected. Define this limit in MB through the data-limit option:

mpirun -np 128 vtune -collect hotspots -data-limit=200 -- ./a.out

Some more information about VTune you can find here.

See also

External links