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.
felix_dt
3
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Nsight Compute slows down Tesla T4 processor clock during profiling | 4 | 973 | May 11, 2020 | |
| Nsight Compute: The frequency is not fixed | 3 | 1254 | May 5, 2024 | |
| SM frequency reported in Nsight Compute | 3 | 1242 | September 1, 2023 | |
| GPU SM Frequency | 2 | 779 | August 15, 2024 | |
| Device frequency | 1 | 843 | January 4, 2023 | |
| Why the Peak FLOP/s in Nsight Compute is much less than white paper provided? | 4 | 973 | February 10, 2023 | |
| Locked Frequency when profiling | 3 | 808 | March 11, 2023 | |
| Elapsed cycles reproted by nsight | 2 | 1071 | April 30, 2020 | |
| Is Cycles dependent on Time or reverse? | 1 | 630 | November 30, 2021 | |
| Is it acceptable to measure kernel performance using Nsight Compute? | 2 | 292 | July 8, 2025 |