- May 1, 2020
- 380
- 538
- 106
@Hulk
While I did the first testing I queried the sensors as often as possible. There I realized two things: The querying itself causes quite some CPU load when done too often. And the sampling frequency is not very steady. That is why I wait at least 10ms before the next query. That causes next to no load and is "accurate enough" for me. And because the sampling frequency is not that uniform I needed to take into account the time frames between two samples. So I have a weighted average.
To your next question: Yes, the frequency is available as well and yes, I like your idea of generating some nice IPC numbers. Will think this through a littlebit.
But what HWInfo measures is something else and I do not know what that is. They seem to be taking clock gating and other power saving measures into account. Because my Ryzen never goes below 1400Mhz IIRC but they are showing that effective clock to be near 0 when idling.
While I did the first testing I queried the sensors as often as possible. There I realized two things: The querying itself causes quite some CPU load when done too often. And the sampling frequency is not very steady. That is why I wait at least 10ms before the next query. That causes next to no load and is "accurate enough" for me. And because the sampling frequency is not that uniform I needed to take into account the time frames between two samples. So I have a weighted average.
To your next question: Yes, the frequency is available as well and yes, I like your idea of generating some nice IPC numbers. Will think this through a littlebit.
But what HWInfo measures is something else and I do not know what that is. They seem to be taking clock gating and other power saving measures into account. Because my Ryzen never goes below 1400Mhz IIRC but they are showing that effective clock to be near 0 when idling.