Skip to content
Snippets Groups Projects
Commit 9c422011 authored by Jan Siwiec's avatar Jan Siwiec
Browse files

Update intel-vtune-amplifier.md

parent 5928212d
Branches
No related tags found
No related merge requests found
Pipeline #39998 passed with warnings
...@@ -27,7 +27,7 @@ $ ml av VTune ...@@ -27,7 +27,7 @@ $ ml av VTune
To profile an application with VTune Amplifier, special kernel modules need to be loaded. The modules are not loaded on the login nodes, thus direct profiling on login nodes is not possible. By default, the kernel modules are not loaded on compute nodes either. In order to have the modules loaded, you need to specify the `vtune=version` PBS resource at job submit. The version is the same as for the environment module. For example, for VTune/2016_update1, use: To profile an application with VTune Amplifier, special kernel modules need to be loaded. The modules are not loaded on the login nodes, thus direct profiling on login nodes is not possible. By default, the kernel modules are not loaded on compute nodes either. In order to have the modules loaded, you need to specify the `vtune=version` PBS resource at job submit. The version is the same as for the environment module. For example, for VTune/2016_update1, use:
```console ```console
$ qsub -q qexp -A OPEN-0-0 -I -l select=1,vtune=2020_update3 $ salloc -p qexp -A PROJECT_ID --nodes=1 --gres=vtune:2020_update3
``` ```
After that, you can verify the modules `sep*`, `pax`, and `vtsspp` are present in the kernel: After that, you can verify the modules `sep*`, `pax`, and `vtsspp` are present in the kernel:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment