You can find information on Nsight Compute’s clock control behavior in the documentation. It is expected that clocks are locked to their base value by default, which is relatively low on e.g. A100, to provide a controlled and deterministic environment for data collection. If you require a specific frequency, you can disable clock control in Nsight Compute and lock the clocks using nvidia-smi externally. Note that profiling without locked clocks can result in incorrect metric values.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Nsight Compute slows down Tesla T4 processor clock during profiling | 5 | 886 | October 12, 2021 | |
| Nsight Compute: The frequency is not fixed | 4 | 1183 | May 19, 2024 | |
| SM frequency reported in Nsight Compute | 4 | 1089 | September 1, 2023 | |
| Elapsed cycles reproted by nsight | 3 | 1014 | October 12, 2021 | |
| Is Cycles dependent on Time or reverse? | 1 | 582 | November 30, 2021 | |
| Nsight leaks a call to lowering GPU clocks even after Nsight has closed | 9 | 688 | October 12, 2021 | |
| Device frequency | 1 | 788 | January 4, 2023 | |
| GPU SM Frequency | 2 | 607 | August 15, 2024 | |
| Why the Peak FLOP/s in Nsight Compute is much less than white paper provided? | 4 | 904 | February 10, 2023 | |
| CUDA profiling Extract the number of clock cycles of a CUDA application execution | 2 | 8556 | August 23, 2011 |