|
@@ -64,16 +64,16 @@
|
|
|
"cell_type": "markdown",
|
|
|
"metadata": {},
|
|
|
"source": [
|
|
|
- "Now, we can **profile** the serial code via Nsight Systems command line (see below example command):\n",
|
|
|
+ "Now, if we **profile** the serial code via Nsight Systems command line (see below example command) and download the report, we can investigate the serial code further.\n",
|
|
|
"\n",
|
|
|
- "`nsys profile -t nvtx --stats=true --force-overwrite true -o miniWeather_1 ./miniWeather1`"
|
|
|
+ "`nsys profile -t nvtx --stats=true --force-overwrite true -o miniWeather_1 ./miniWeather`"
|
|
|
]
|
|
|
},
|
|
|
{
|
|
|
"cell_type": "markdown",
|
|
|
"metadata": {},
|
|
|
"source": [
|
|
|
- "We download the profiler output (`miniWeather_1.qdrep`) and open it via the Nsight Systems UI. From the timeline view, checkout the NVTX markers displays as part of threads. **Why are we using NVTX?** Please see the section on [Using NVIDIA Tools Extension (NVTX)](profiling-c.ipynb#Using-NVIDIA-Tools-Extension-(NVTX))\n",
|
|
|
+ "For the example command above, we download the profiler output (`miniWeather_1.qdrep`) and open it via the Nsight Systems UI. From the timeline view, checkout the NVTX markers displays as part of threads. **Why are we using NVTX?** Please see the section on [Using NVIDIA Tools Extension (NVTX)](profiling-c.ipynb#Using-NVIDIA-Tools-Extension-(NVTX))\n",
|
|
|
"\n",
|
|
|
"<img src=\"images/e1-nvtx_gui.png\">\n",
|
|
|
"\n",
|