@liuyis I used your advice from the other thread to get the CUDA runtime events by attaching nsys to the background process, but I still am not able to see the page fault data while profiling inside the container. Could you please have a look at the nsys-rep file?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| How to Display CPU and GPU Page Faults in NSYS Output for Unified Memory on Grace Hopper? | 7 | 278 | January 29, 2025 | |
| How to output uvm page fault memory address to the terminal via using nsys 2024.1.? | 8 | 690 | February 15, 2024 | |
| Does not contain CUDA Unified Memory CPU page faults data | 16 | 1222 | March 8, 2024 | |
| --cuda-um-gpu-page-faults and --cuda-um-cpu-page-faults is not regocnized | 6 | 255 | September 1, 2024 | |
| Nsight system not report unified memory page fault statistics in summery | 3 | 1938 | March 29, 2024 | |
| [Question] NSys CUDA Profiler - Page fault size | 5 | 83 | August 28, 2024 | |
| Detail page fault tracking via nsys | 2 | 598 | February 14, 2024 | |
| Missing CUDA runtime events from nsys report | 7 | 164 | April 17, 2025 | |
| Page fault profiling | 2 | 983 | September 6, 2023 | |
| [Question] NSys CUDA Profiler - Page Migration and Number of CPU/GPU page faults | 1 | 1021 | June 23, 2023 |