Discussion in 'Videocards - AMD Radeon' started by OnnA, Aug 15, 2017.
A little improvement
Vega 64 starting at 484€ also + top Pick Sapphire Nitro+ at 499€
RTX 2070 starting at 519€
Note: Here is used non-AIB reference Blower Vega 64 (No HBCC?), Nitro+ is delivering better FPS.
Oh wow, undervolting does help! I undervolted my card by 70mV and for the first time saw my GPU core hit 1578MHz, it used to be around 1530MHz max.....due to enclosed case airflow being decent but not good. I have Memory at 990MHz and tried some benchmarks and there is some improvement. When the warranty for my card is over, I'll do like what I did with my 2x R9 290X, water cool that babdboy!
Yeah Vega's stock settings push quite a bit of voltage on the cards which translates into heat. Setting the power limit and voltage settings can really improve the clock speed sustainability and even allow for higher overclocking depending on how good the GPU is which is going to vary a bit but the cards have a lot of different factors for how it's clocking up or down so the more limits you can remove the better the overall performance will be.
It helps that the binning is generally pretty good so most of them undervolt nicely and see improvements from this rather than any trade-offs between power usage and draw and clock speeds and performance.
.... wrong thread
Hi guys .
Why my gpu cant reach p7 state ? not enough voltage or where is the problem or my thinking is bad and benchmark will not squeeze the max
It's probably not entirely correct but the way I see it p7 is the boost or max clock which the drivers use as a target speed but never really sustains thus the actual performance figure for 3D workloads is generally right in the middle between p6 and p7 regardless of what you try to do short of forcing it. (Setting p6 or p7 as the minimum allowed state which I would avoid.)
I've been down to 50c core clock temps and having p7 at 1500mhz with 1.1v which is well and above what is needed for stability and it still had the same behavior usually sitting at 1460 - 1480 Mhz since it works not only via various thresholds and limits but also total workload which however around 85 - 95% though 1600mhz and 1700mhz for p6 and p7 respectively should still be plenty fast if stable for when the odd spike or boost pushes it to 1700+ which can still happen.
Just something with how these cards work, p6 is the higher clock state and 3D workloads and then p7 is something like boost or max but it's never really sustained and it always drops to somewhere in-between the two.
(Which you can still have a higher p6 state instead and get really good performance that way but it might take some testing to find the best stable values if you push for a higher clock speed in this way.)
EDIT: Shadows of the Tomb Raider and Wattman via Vega 56 pulse and a nice cool day allowing for lower ambient temps.
1450Mhz for p6 and 1500Mhz for p7 with 1.050v for p6 and 1.1v for p7 which should be fine. Vega 56 using the Hynix memory so mem clocks is at 850Mhz from 800Mhz stock.
Fan is around 2400rpm trying to hit around 55 - 65% speeds and what else, I think that's most of it.
Was testing how it would operate with a high workload but lower temps and power limits at +50% too and seeing the results and yeah near 100% load and it tries to hit p7 but as it drops it goes to p6 instead usually being right in the middle of the two states.
(Due to HBM2 clocks I usually keep around 1500 - 1550 Mhz since the gains aren't as good as 1Ghz+ mem clocks via Samsung chips or a full Vega 64 so it's not much of a reduction really.)
Whilst poking around i came across this curious (what i presume is support to be a registry dword ) KMD_PrimitiveShaderSupport.
kinda interesting to see on windows.
rawhex of the string in the atikmdag
4B 00 4D 00 44 00 5F 00 50 00 72 00 69 00 6D 00 69 00 74 00 69 00 76 00 65 00 53 00 68 00 61 00 64 00 65 00 72 00 53 00 75 00 70 00 70 00 6F 00 72 00 74
Where did you find this?
Just wait for December Driver
(+30% free performance?)
I'm not kidding
and it's like this:
Oh I think you are being generous in your prediction there, Onna.
^^ Like always
no , the raw hex is just the string i found in the atikmdag , so its easier to find in the binary for those inclined , there are a ton of KMD variables other than this one
I assume for kmd_primitiveshadersupport its a boolean (0 or 1) dword
I not sure i would expect it to do anything just yet, since primitiveshaders haven't been exposed via any apis like vulkan just yet.
and if you put those string into translator then: KMD_PrimitiveShaderSupport pops out (on the right panel lol)
So you searched through Hex words
Please inform Us of Your findings.