• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

AMD RYZEN 7 5800x3D not usage -w 100%

Indeed the lower core clock only corresponds to active cores (Residency C0)
But power plan also makes a difference in core count activity. How many cores are at “active” (C0) state or “halt/power off” states (C1/C6) at any given moment of any load and how cores react to (new) loads. Especially small and short ones.

You can watch over time the Core residency states and the active core count in HWiNFO.

Also, I can’t say it enough, when using HWiNFO sensor window the setting “Snapshot CPU Polling” must be ON at all times. Otherwise CPU parameters are disturbed when the software is polling values and CPU core states and clocks are messed up.

EDIT
Forgot to clarify and it’s related to what @tabascosauz said, that effective clocks on HWiNFO contains all 3 CPU core states (C0/C1/C6) unlike “regular” core clocks that is based on C0 only.
 
Last edited:
Indeed the lower core clock only corresponds to active cores (Residency C0)
But power plan also makes a difference in core count activity. How many cores are at “active” (C0) state or “halt/power off” states (C1/C6) at any given moment of any load and how cores react to (new) loads. Especially small and short ones.

You can watch over time the Core residency states and the active core count in HWiNFO.

Also, I can’t say it enough, when using HWiNFO sensor window the setting “Snapshot CPU Polling” must be ON at all times. Otherwise CPU parameters are disturbed when the software is polling values and CPU core states and clocks are messed up.

EDIT
Forgot to clarify and it’s related to what @tabascosauz said, that effective clocks on HWiNFO contains all 3 CPU core states (C0/C1/C6) unlike “regular” core clocks that is based on C0 only.
Agreed, though I still think that the Balanced power plan works best. As the name suggests, it's the best balance between idle and high power states. Performance and Ultimate Performance are overkill.
 
It won't let the CPU clock down in idle, though.
Screenshot 2024-01-04 170630.png


No issues here with Ultimate performance mode. My idle is a bit on the high side, but no biggie. It still works.
This is probably due to me taking the measurement a few seconds after stopping my simulation for this screenshot and resuming the simulation promptly. Otherwise, the idle usually hovers 5 - 7w at a time.
 
No issues here with Ultimate performance mode. My idle is a bit on the high side, but no biggie. It still works.
That's the thing - the CPU idles in a higher state than it would in "balanced". If you're fine with that, that's another story.

Edit: I just noticed that "performance" or "ultimate performance" doesn't improve my system's performance or responsiveness at all, while increasing idle power by a touch. Not worth it, imo, but each to their own.
 
Guys how to fix cpu and gpu usage +100%
in vain, if I reduce it, it's the same fps as if I increased the resolution..
Usage isn't supposed to be 100% all the time FYI, in this case you're at such high framerates you're hitting a wall anyway, from the game engine or just CPU bottleneck (core 16 at 92%) because nearly 1000fps is a LOT.
 
GPU VRM is super happy to provide thousands of FPS for hours on end :D

You can tell by the squeal :laugh:
 
No need for one, it is true :D

X3D loves tight timings too :)

now what?

How to fix input lag:???


Local: local host server,
server: online server:
mouse: Logitech G Pro X Superlight
Keyboard: ROG Falchion Ace
Monitor: XL2566K 360Hz
Thank you
 

Attachments

  • local.jpg
    local.jpg
    192.5 KB · Views: 58
  • server.jpg
    server.jpg
    214.8 KB · Views: 60
Just a bit of a warning, if you go too low on quality, GPU will downclock to 2D/Low 3D clock decreasing performance and increasing input lag.
In such case, try increasing resolution (via for example : VSR or DSR).
 
Just a bit of a warning, if you go too low on quality, GPU will downclock to 2D/Low 3D clock decreasing performance and increasing input lag.
In such case, try increasing resolution (via for example : VSR or DSR).

Any idea, should we set it in the nvidia control panel?
 
Back
Top