I really wish I could see that “CUDA API” line, but I can’t. Any hints on how to get it? I followed these instructions: " When the Collect GPU Memory Usage option is selected from the Collect CUDA trace option set, Nsight Systems will track CUDA GPU memory allocations and deallocations and present a graph of this information in the timeline"
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Cuda runtime call after driver api call, excessive overhead | 17 | 2292 | December 24, 2021 | |
| My GPU Became Slower... after 1 month of not testing cuda | 18 | 12420 | August 23, 2010 | |
| kernel call overhead: timing results overhead is large for small # of calls | 16 | 8031 | March 8, 2013 | |
| Low or normal performance? | 20 | 1454 | November 13, 2020 | |
| reduce overhead of launching a new thread block | 15 | 4894 | February 15, 2018 | |
| CUDA setup times (create context, malloc, destroy context) some measurements included | 19 | 23318 | July 8, 2011 | |
| Why would code run 1.7x faster when run with nvprof than without? | 35 | 3627 | December 28, 2017 | |
| why cudaGetDeviceProperties and cudaMallocPitch consume a lot of time | 18 | 2589 | January 9, 2017 | |
| Long delays on CUDA app startup causing Nsight System to fail on startup | 37 | 2412 | May 19, 2023 | |
| First kernel execution takes longer | 8 | 3012 | December 8, 2014 |