Nsight System profiles CUDA memory copies and when .qdrep file generated through nsys is loaded into the Nsight System GUI, Source and Destination device IDs can be seen for peer-to-peer memcopies. Whereas, if nsys --export=sqlite option is used, the CUPTI_ACTIVITY_KIND_MEMCPY table is missing these src and destination device IDs. Is there any other option in nsys tracing or writing a query in the sqlite tables to extract this information? Or can these ids can be added to CUPTI_ACTIVITY_KIND_MEMCPY table for sqlite format?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Is there any kind of documentation for Nsight Systems' sqlite output? | 3 | 1734 | September 6, 2021 | |
| Nsys measure memory | 7 | 1927 | April 15, 2022 | |
| Nsys does not show CUDA kernels | 6 | 1294 | December 12, 2022 | |
| Where is "nsys export" in Nsight Systems 2020.2? | 1 | 1113 | May 20, 2020 | |
| Finding information about nsys-rep file | 2 | 913 | October 29, 2022 | |
| "Analysis Summary" data in Nsight Systems GUI | 1 | 856 | February 22, 2022 | |
| Cuda graph trace export | 3 | 1020 | February 29, 2024 | |
| Sqlite empty data column in GENERIC_EVENTS | 4 | 13 | January 30, 2025 | |
| Nsys doesn't dump .sqlite even after using --export | 10 | 2155 | December 16, 2024 | |
| Nsys profiling does not contain CUDA kernel data | 3 | 823 | November 5, 2023 |