Search results

  1. T

    CPU Package Power at very high polling rates above power limit

    I compared average CPU Package Power at 100 ms and 1000 ms polling rate, running the same reproducible load (Handbrake encode). They match close enough, so I assume that the CPU power counter and time-delta likely are trustworthy while throttling isn't instant enough to keep power from increase...
  2. T

    CPU Package Power at very high polling rates above power limit

    My settings are PL1 = PL2 = 253 W. So the default Tau of 56s is essentially unused, except for changing the trigger sensor from PL2 to PL1 after some time.
  3. T

    CPU Package Power at very high polling rates above power limit

    So I understand that for "CPU Package Power" the CPU reports Joules consumed per time-frame and HWinfo read out the value, divides by said time-frame and clears the CPU register (or it is automatically cleared upon readout)!? Assuming that the energy consumed in Joules is correct then either...
  4. T

    CPU Package Power at very high polling rates above power limit

    Thank you for the explanations. Does HWinfo calculate power from other numbers (VID + current), or does it read out a CPU register where the CPU calculated power itself?
  5. T

    CPU Package Power at very high polling rates above power limit

    I still wonder if measuring higher power than the power limit is an imprecision or the CPU not being capable of throttling fast enough to stay below the power limit? The reason why I even tried higher polling rates is because I encountered some loads where maximum power is reported considerably...
  6. T

    CPU Package Power at very high polling rates above power limit

    Hello. At very high polling rates HWinfo measures CPU Package Power higher than the power limit, sometimes even without the power limit sensors triggering. These screenshots were made on my 13900K with the power limit set to 253 W: Is this expected behavior?
  7. T

    IA Power Limit vs. CPU Power reading vs. Poll period

    "Average between two sampling points" might then be what makes measuring Folding@home so difficult. It running into a permanent throttling power-limit while the CPU Package Power sensor reads 7-10 W *below* the power-limit was something I didn't expect/look out for. And those "short spikes"...
  8. T

    IA Power Limit vs. CPU Power reading vs. Poll period

    I originally noticed this without running other applications. Throttlestop was only added later to have something to compare. And even when TS clears the flag for itself the Hwinfo flag stays semi-permanently on. At 20 ms it sometimes says "No" for a very short time (long enough to set the...
  9. T

    IA Power Limit vs. CPU Power reading vs. Poll period

    Turns out that the Folding@home load I used for this measurement allows other processes (like HWinfo) to take over CPU load and thus lower FAH's CPU time even when FAH runs at Realtime priority and HWinfo at low/idle priority. So this seems to be why fast polling of HWinfo keeps FAH from...
  10. T

    IA Power Limit vs. CPU Power reading vs. Poll period

    Hello. Even at 20 ms poll rate I run into this situation where HWinfo's IA Limit for PL2 stays nearly *permanently* on and effective clocks shows some throttling, while the CPU Package Power reading never hits the 253 W power limit even once. Comparing via Throttlestop software shows its Power...
  11. T

    CPU Turbo Max per core

    But for the BIOS "bug" the power budget doesn't change from reboot to reboot. After the 2nd reboot it works properly. - Change per core max of a core from 55 to 58. - Save and reboot: SSE = 58, AVX = 55 - (Reenter BIOS, save and) reboot with no changes made (!): SSE = 58, AVX = 58 And for the...
  12. T

    CPU Turbo Max per core

    I am using an AVX offset of 0 and negative AVX offset rather seems to apply to "Turbo Ratio Limits - AVX2". And with the BIOS bug I just encountered it even even limits AVX load to lower ratios until the second reboot when per-core ratios are increased. Example: Core 0's ratio is increased...
  13. T

    CPU Turbo Max per core

    Coming back to this after noticing a bug in my BIOS that reveals an apparent internal AVX list not shown by HWinfo. Currently HWinfo lists: Maximum Per-core Ratio Limits (Fused) Maximum Per-core Ratio Limits (Current) I suspect that the BIOS also includes a "Maximum Per-core Ratio Limits AVX...
  14. T

    Audio notification/alarm

    I just heard it working in practice. Thanks again.
  15. T

    Audio notification/alarm

    Ah, I thought it would only trigger for each increasing count and that the "Trigger only once" option would then make it only trigger on the first count.
  16. T

    Audio notification/alarm

    Great stuff, thank you! It cannot be made to play/loop for a prolonged period of time for a single trigger event other than using a long alarm sound, or can it?
  17. T

    Audio notification/alarm

    Hello. I am currently running stability tests with HWinfo monitoring WHEAs in the background. Unfortunately I couldn't find a way to enable an audible notification/alarm when these occur. So instead I have to remember opening the HWinfo window from time to time. If this isn't already available...
  18. T

    VRM monitoring on GIGABYTE Z690, Z790

    Ah, so my Z790 Aero G just doesn't support current and power sensors then. Thanks again.
  19. T

    Intel "Thermal Velocity Boost"

    Thank you.
  20. T

    VRM monitoring on GIGABYTE Z690, Z790

    Thanks, so this is about VRM temperature monitoring, not other parameters?
Back
Top