Nsight leaks a call to lowering GPU clocks even after Nsight has closed

Developer Tools Nsight Graphics
1

Hi,

GPU boosts to 1700MHz running my application before ever opening Nsight.
During Nsight profiling clocks are pegged at 1200MHz - this is expected.
After closing Nsight, no application running after this time can increase clocks above 1200MHz, resulting in significantly poorer performance.

Rebooting the machine after running Nsight is the only way to get back to “normal” levels of performance.

Thanks,

Adam

2

Hi Adam,

Thank you for reporting this!

Just so we can try to get a good repro, can you provide us with your: GPU SKU, Driver version, OS Version, and Nsight Graphics version?

Thanks!
Seth

3

Titan V
416.41 (private build)
Windows 10 1809 (17763.55)
Nsight Graphics installer: NVIDIA_Nsight_Graphics_2018.6.0.18299.msi

And if it’s relevant, the workload being profiled was a D3D12 DXR application.

Thanks!

4

Thanks Adam! We’ll work on a repro and get back to you. I’ll let you know if we run into any issues or need any more info.

Have a great weekend!

Thanks,
Seth

5

Actually, one more thing - were you using the profiling activity or the GPU trace activity?

6

GPU Trace

7

Hi Adam,

We were able to reproduce the issue on our side. Thanks again for all the info!

Unfortunately, it looks like it may take a couple of weeks to fix. I’ll keep you updated with any changes/progress!

Thanks,
Seth

8

Thanks Seth, I’ll keep an eye out for the next set of Release Notes!

9

Hi Adam,

Wanted to update you and say we fixed this issue in the local case in the 2018.7 release. Thanks again for reporting it!

Remote profiling ended up being a bit more complicated, but will post back here again when we release that fix.

Thanks!
Seth