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 | 1782 | September 6, 2021 | |
| SKIPPED: Sqlite does not contain GPU memory data | 2 | 756 | November 22, 2023 | |
| Sqlite does not contain CUDA kernel data | 12 | 3897 | April 28, 2023 | |
| Nsys measure memory | 7 | 1979 | April 15, 2022 | |
| Nsys not creating nsys-rep file | 5 | 365 | March 26, 2025 | |
| How to mapping between GPU cards with GPU metrics in nsys profile output | 7 | 86 | July 29, 2025 | |
| Generating CUPTI_* tables with nsys | 25 | 1744 | January 12, 2023 | |
| Nsight nsys not collecting any CUDA kernel data (2023.1.2.43-32377213v0) | 19 | 2739 | September 14, 2023 | |
| Nsys cli cannot trace cuda | 5 | 2460 | May 13, 2022 | |
| "Exportation error: Version number is invalid" when doing nsys stats | 1 | 256 | June 5, 2024 |