3 ms·
That's pretty inaccurate as a rule. TDPs are specified for a standard graphics workload. Compute tasks can easily draw between 50% and 150% of the rated TDP.
by paulmd 10y ago
That's pretty inaccurate as a rule. TDPs are specified for a standard graphics workload. Compute tasks can easily draw between 50% and 150% of the rated TDP. A given task may bottleneck on bandwidth or some other limit long before it hits a high level of TDP (which may fall into the generic 'unsuited for GPU' category and can never really be optimized).
So apart from a generic inspiration to keep going further, this really does nothing for you. In fact you may still have further performance gains possible after this heuristic tells you to stop.
- jacquesm 10y agoI usually have a pretty good idea how much utilization I should see, it's just a quick way to make sure I get what I'm aiming for and it has definitely helped me on a number of occasions when performance was disappointing to point out the GPU was simply starved. Memory access for a GPU is everything, even one detail wrong and you could easily get a 50% or more performance penalty so it is handy to have a quick confirmation that you're in the ballpark. It's not suitable as a detailed profiler.