rsnt_translations
56,430
edits
OpenACC Tutorial - Adding directives: Difference between revisions
OpenACC Tutorial - Adding directives (view source)
Revision as of 15:33, 12 December 2022
, 1 year agoMarked this version for translation
(Here will be the introduction to NVVP) |
(Marked this version for translation) |
||
| Line 323: | Line 323: | ||
The results are correct. However, not only do we not get any speed up, but we rather get a slow down by a factor of almost 4! Let's profile the code again using NVidia's visual profiler (<tt>nvvp</tt>). | The results are correct. However, not only do we not get any speed up, but we rather get a slow down by a factor of almost 4! Let's profile the code again using NVidia's visual profiler (<tt>nvvp</tt>). | ||
=== NVIDIA Visual Profiler === | === NVIDIA Visual Profiler === <!--T:52--> | ||
[[File:Nvvp-pic0.png|thumbnail|300px|NVVP profiler|right]] | [[File:Nvvp-pic0.png|thumbnail|300px|NVVP profiler|right]] | ||
[[File:Nvvp-pic1.png|thumbnail|300px|Browse for the executable you want to profile|right]] | [[File:Nvvp-pic1.png|thumbnail|300px|Browse for the executable you want to profile|right]] | ||
<!--T:53--> | |||
One graphical profiler available for OpenACC applications is the | One graphical profiler available for OpenACC applications is the | ||
[https://developer.nvidia.com/nvidia-visual-profiler NVIDIA Visual Profiler (NVVP)]. | [https://developer.nvidia.com/nvidia-visual-profiler NVIDIA Visual Profiler (NVVP)]. | ||
| Line 332: | Line 333: | ||
Consequently, if the executable is not using the GPU, you will get no result from this profiler. | Consequently, if the executable is not using the GPU, you will get no result from this profiler. | ||
<!--T:54--> | |||
When [[Visualization/en#Remote_windows_with_X11-forwarding|X11 is forwarded to an X-Server]], or when using a [[VNC|Linux desktop environment]] (also via [[JupyterHub#Desktop|JupyterHub]] with two (2) CPU cores, 5000M of memory and one (1) GPU), | When [[Visualization/en#Remote_windows_with_X11-forwarding|X11 is forwarded to an X-Server]], or when using a [[VNC|Linux desktop environment]] (also via [[JupyterHub#Desktop|JupyterHub]] with two (2) CPU cores, 5000M of memory and one (1) GPU), | ||
it is possible to launch the NVVP from a terminal: | it is possible to launch the NVVP from a terminal: | ||
| Line 343: | Line 345: | ||
<translate> | <translate> | ||
<!--T:55--> | |||
# After the NVVP startup window, you get prompted for a ''Workspace'' directory, which will be used for temporary files. Replace <code>home</code> with <code>scratch</code> in the suggested path. Then click ''OK''. | # After the NVVP startup window, you get prompted for a ''Workspace'' directory, which will be used for temporary files. Replace <code>home</code> with <code>scratch</code> in the suggested path. Then click ''OK''. | ||
# Select ''File > New Session'', or click on the corresponding button in the toolbar. | # Select ''File > New Session'', or click on the corresponding button in the toolbar. | ||
| Line 352: | Line 355: | ||
# Click ''Finish'' to start profiling the executable. | # Click ''Finish'' to start profiling the executable. | ||
<!--T:56--> | |||
This can be done with the following steps: | This can be done with the following steps: | ||
# Start <tt>nvvp</tt> with the command <tt>nvvp &</tt> (the <tt>&</tt> sign is to start it in the background) | # Start <tt>nvvp</tt> with the command <tt>nvvp &</tt> (the <tt>&</tt> sign is to start it in the background) | ||