I’ve noticed that my L2 cache hit rate exceeds 100%. Has anyone encountered this before and knows what it means?
Small deviations from the logically correct range are an expected measurement error if a metric is composed of multiple counters, and those are collected across different replay passes. Having clock and cache control enabled helps to reduce the error, but it can still occur due to non-determinism in the kernel or HW. You can try to further reduce the measurement error by collecting the metric by itself, but there is no guarantee if it’s not collectable in a single replay pass.
You can refer to https://docs.nvidia.com/nsight-compute/ProfilingGuide/index.html#range-and-precision for further details.