Throttling detection needed in Windows about windows-dev-performance

[randomascii]

This issue has recently become particularly personally interesting for me because my work laptop has started intermittently throttling. I don't know if it is thermal throttling, power throttling, or something else. I suspect thermal throttling, perhaps due to thermal paste or some other aspect of the laptop degrading after ~four years of use.

Diagnosing this was tricky. I initially noticed intermittent sluggishness, then I went to Task Manager which showed the CPU was only ~27% busy. At first that seemed odd that the computer would feel so sluggish when 73% of the CPU time was available and I thought maybe the sluggishness was elsewhere in the system. But then I noticed that the CPU was running at ~0.8 GHz. Then I remembered that Task Manager shows percentage busy as a percentage of the nominally available CPU cycles, so in fact the CPU was 100% busy at 0.8 GHz and the sluggishness was from the low speed.

Which is to say, it took rather too much math (I had to multiply the 27% busy amount by the norminal frequency divided by the actual frequency in order to tell that the CPU was in fact fully occupied) and too much guessing ("I guess it's thermal throttling?") and I know that the CPU records its temperature and records when it hits thermal limits.

So, please show the throttling reasons. And please consider changing how Task Manager displays CPU usage. It rarely makes any difference during normal operation, but when throttling happens it is extremely confusing.

[AvriMSFT]

Hey @randomascii thanks for submitting this issue and apologies for the delayed response! I've reached out to some folks on the issue and will get back to you with updates once I have them. Thanks for your patience!

[Eli-Black-Work]

Having some sort of visual indicator in Process Manager that indicates CPU throttling is a great idea 🙂

[stolk]

Ugh... I will have to inform my customers, that TurboLEDz no longer works under Windows. Disappointing.

The OS itself is still able to retrieve core frequencies, though, as you can see them in the Task-Manager.

I bet this was done to stop an exploit: if you can measure how busy cores are, you can get a modicum of information on secrets.

Frankly, as this call req'd administrator rights already, microsoft should have left this one alone.

[jwatte]

It's fine, you can just throw in a bogomips loop of 100,000 dry iterations before each vblank in your game, and time how long it takes using HPET or something. You'll be able to detect down-clocked CPUs that way.
Yes, that's a terrible idea. Yes, that's how it will be done, as long as the OS lies to us.