Browsing though the previous topics in the forum, one repeated point I saw was SilverAzide and others having to explain and re-explain time-based vs. utility-based methods for CPU usage/utilization. Silver gives a great summary here, so just to hopefully (re-)summarize it with the relevant measures:
Time-based: Utility-based:It seems like for some new Rainmeter users, they feel like there' must be so many complicated ways to get CPU usage/utilization, but sticking to native Rainmeter methods, it roughly boils down to those, yeah? Not to blame new users, since it was Microsoft that changed things around.
There's no one "correct" value, and they're all measuring similar but different things. I was going to make a dive into it, logging all the values and making various calculations for various situations, but monitoring them over the day (with the below HWiNFO as well), they're all pretty close to each other no matter what situation I throw at it. I'm on Win10 and not 11, but again, it's probably going to be one of the above measures in the end. It's not some static value you can perfectly hone in on, it's always going to change faster than any method can capture.
Also setting up HWiNFO now is decidedly faster/easier using the registry values compared to the old method, just following the guide in the docs. I could see the old hex codes being a pain for some if you're monitoring many components and values, but for example, now it's just:
A one-time set up of the couple HWiNFO settings and choosing what you want in the HWiNFO Gadget section with the indices placed as N completes the connection. Like the guide mentions, no more extra steps of the plugin or hex codes, just those two spots for users to look at and a simple number for the index in the the measure. And HWiNFO has handy tooltips in the sensor panel explaining what each value is.
Time-based:
Code:
[MeasureCPU_Rainmeter_Standard] Measure=CPU[MeasureCPU_UsageMon_AliasCPU] Measure=Plugin Plugin=UsageMonitor Alias=CPUCode:
[MeasureCPU_UsageMon_Utility] Measure=Plugin Plugin=UsageMonitor Category=Processor Information Counter=% Processor Utility Name=0,_Total MinValue=0 MaxValue=100There's no one "correct" value, and they're all measuring similar but different things. I was going to make a dive into it, logging all the values and making various calculations for various situations, but monitoring them over the day (with the below HWiNFO as well), they're all pretty close to each other no matter what situation I throw at it. I'm on Win10 and not 11, but again, it's probably going to be one of the above measures in the end. It's not some static value you can perfectly hone in on, it's always going to change faster than any method can capture.
Also setting up HWiNFO now is decidedly faster/easier using the registry values compared to the old method, just following the guide in the docs. I could see the old hex codes being a pain for some if you're monitoring many components and values, but for example, now it's just:
Code:
[MeasureCPU_HWiNFO_Utility] Measure=Registry RegHKey=HKEY_CURRENT_USER RegKey=SOFTWARE\HWiNFO64\VSB RegValue=ValueRaw0 ; SensorN, LabelN, ValueN, ValueRawNStatistics: Posted by Alex88 — Yesterday, 10:58 pm — Replies 0 — Views 29