Erm, I'm not sure that logic works. Trying to finagle some number by multiplying things around isn't going to get you anything meaningful, especially if you have an Intel hybrid CPU.OK, I get itSo I guess I'll just leave things as they are for the moment, no need for a stress test. If someday I see my CPU% going over 100%, I'll just take note of the highest value and I'll increase MaxValue accordingly. That should do the trick.
![;-)]( "Wink")
Thanks for your help!
So I guess I'll just leave things as they are for the moment, no need for a stress test. If someday I see my CPU% going over 100%, I'll just take note of the highest value and I'll increase MaxValue accordingly. That should do the trick. If you are of the mind set (like many folks are) that your CPU usage shouldn't exceed 100%, then you must use the time-based performance counters. The problem is that MS "broke" the time-based counters in Win11 22H2 and at this point it looks like they have no intention of fixing the problem.
You do have a work-around.
HWiNFO v7.46 and later implements a correction to the time-based counters. So instead of using the Rainmeter's CPU or UsageMonitor measures, use HWiNFO to get this data. Just be aware that Task Manager doesn't use time-based counters (and hasn't since Win8) so what you see there won't match what HWiNFO (or Windows PerfMon) will give you.
Statistics: Posted by SilverAzide — Today, 12:22 am