Versionen im Vergleich

Schlüssel

  • Diese Zeile wurde hinzugefügt.
  • Diese Zeile wurde entfernt.
  • Formatierung wurde geändert.

...

Codeblock
languagebash
module add vtune/XXXX

Intro:
https://ci.spdk.io/download/2019-summit-prc/02_Presentation_02_VTune_and_Analyzers_Overview_Sri.pdf
www.intel.com/content/www/us/en/docs/vtune-profiler/get-started-guide/2023/linux-os.html

...

Codeblock
languagebash
vtune -help

Run VTune via the command line interface

Run your application with VTune wrapper as follows:
www.intel.com/content/www/us/en/docs/vtune-profiler/user-guide/2023-0/command-line-interface.html

...

Open 127.0.0.1:55055 in your browser (allow security exception, if first time set initial password).

In 1st "Welcome" VTune tab (run MPI parallel Performance Snapshot):

...

Codeblock
languagebash
#!/bin/bash

echo
"Target
process PID: ${VTUNE_TARGET_PID}"

# Run VTune collector (here with 4 MPI ranks)
mpirun -np 4 "$@"

Under HOW, run: Performance Snapshot.
(After completion/result finalization a 2nd result tab opens automatically.)

...

-> Here you find several analysis results e.g. the HPC Perf. Characterization.
-> Under Performance Snapshot - depending on the snapshot outcome - VTune suggests (see % in the figure below) more detailed follow-up analysis types:

...

-> Expand sub-tab Top-down Tree
--> In Function Stack expand the "_start" function and expand further down to the "main" function (first with an entry in the source file column)
--> In the source file column double-click on "filename.c" of the "main" function

-> In the new sub-tab "filename.c" scroll down to the line with maximal CPU Time: Total to find hotspot hotspots in the main function

To quit the debug session press "Exit" in the VTune "Menu" (upper left symbol of "three horizontal bars"). Then close the browser page. Exit your compute node via CTRL+D and kill your interactive job:

...