[TOOL] Radeon VII PowerPlay Table Generator (OC, UV, Fan Curve)

[CMMChris]

Since apparently there is quite a big demand for it, I am now starting an official topic for my Radeon VII PowerPlay Table generator for macOS. It's a simple Excel spreadsheet where you can change the settings to your desired values. The result is a PowerPlay Table you can inject via Clover on your GPUs PCI path (example below). In Clover you can also use "PrimaryGPU" instead of the PCI path as target device.

Recommendation: Set these device properties in addition to your PowerPlayTable. They come from the Mac Pro 2019 Pro Vega II framebuffer and will increase your Geekbench scores significantly.

<key>ATY,EFIVersion</key>
<data>MDEuMDAuMzE4MA==</data>
<key>CFG_NVV</key>
<integer>2</integer>
<key>CFG_PTPL2_CNT</key>
<integer>16</integer>
<key>CFG_PTPL2_MAX</key>
<integer>300</integer>
<key>CFG_PTPL2_MIN</key>
<integer>90</integer>
<key>CFG_TPS1S</key>
<integer>1</integer>
<key>PP_ACDCGpioDisabled</key>
<integer>0</integer>
<key>PP_DiDtSQPatternWidthOverride</key>
<integer>14</integer>
<key>PP_DiDtSQStallPatternOverride</key>
<integer>16383</integer>
<key>PP_DisableDIDT</key>
<integer>0</integer>
<key>PP_DisablePCCLimitControl</key>
<integer>1</integer>
<key>PP_FclkGfxClkRatio</key>
<integer>1036831949</integer>
<key>PP_PhmUseDummyBackEnd</key>
<integer>0</integer>
<key>PP_WorkLoadPolicyMask</key>
<integer>1</integer>

If you have a good power supply and decent airflow in your case you can also use

<key>PP_DisablePowerContainment</key>
<integer>1</integer>

Here is how the PowerPlay Table Generator looks like:

 

It's possible to change GPU Clock, HBM Clock, GPU Voltage, SoC Voltage, SoC Clock, Power Limit, TDC Limit for GPU, TDC Limit for SoC as well as the Fan Curve. Something that's not working is ZeroRPM due to driver limitations. Turning those parameters on has no effect.
The pre-set values are optimized for the vast majority of cards and use cases (changed Fan curve and UV as well as 1100MHz HBM OC). Please adjust if you have any issues.

 

Warning: I am not responsible for any damaged cards by setting wrong / too high values. If you don't know what you are doing, don't touch it.

 

Enjoy!

 

 

RadeonVII-PPT-Generator.xlsx.zip

Edited April 14, 2020 by CMMChris

[iTTT]

 

hi CMMChris,

 

thats a very good tool.

boot by Clover, now my R VII get 55802 scores in LuxMartk.

 

i need to make a SSDT for this PPT if i use OpenCore.

So do you know how to convert those Clover output data to SSDT format?

 

thanks so much.

[HmO]

4 hours ago, iTTT said:

 

hi CMMChris,

 

thats a very good tool.

boot by Clover, now my R VII get 55802 scores in LuxMartk.

 

i need to make a SSDT for this PPT if i use OpenCore.

So do you know how to convert those Clover output data to SSDT format?

 

thanks so much.

Just add PP_PhmSoftPowerPlayTable into Properties for your GPU 

[iTTT]

2 hours ago, HmO said:

Just add PP_PhmSoftPowerPlayTable into Properties for your GPU 

 

 

 

 

 

 

 

 

 

that works. thanks so much.

 

 

 

 

 

[thunder72fr]

No issue with conflig.plist on my Hackintosh (8700k - Radeon VII):

 

        <key>Properties</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
            <dict>
                <key>@2,AAPL,boot-display</key>
                <integer>1</integer>
                <key>PP_DisableClockStretcher</key>
                <integer>1</integer>
                <key>PP_DisablePowerContainment</key>
                <integer>1</integer>
                <key>PP_DisableULV</key>
                <integer>1</integer>
                <key>PP_EnableUploadFirmware</key>
                <integer>0</integer>
                <key>PP_Falcon_QuickTransition_Enable</key>
                <integer>1</integer>
                <key>PP_GfxOffControl</key>
                <integer>0</integer>
                <key>PP_PhmSoftPowerPlayTable</key>
                <data>
                wgYLAALCBjQIAACkNQAAfAAJAAAAGqoAqgCqAAAAAAB2
                AAELAAAACQcAAG4EAADMAwAAzAMAAMwDAADoAwAAyQQA
                AG4EAABuBAAANAQAACoDAAAAAAAAAAAAAAAAAAAAAAAA
                AAAAALwCAABmAQAANgEAADYBAAA2AQAAXgEAACYCAABm
                AQAAZgEAAJMAAAAOAQAAAAAAAAAAAAAAAAAAAAAAAAAA
                AAABDgAAAAEBAQEBAQEBAQABAQEBAAAAAAAAAAAAAAAA
                AAAAAAAAHQAAAJgIAACYCAAAmAgAANUDAACYCAAA1QMA
                AJgIAADVAwAAsAQAABQAAAAKDwAACg8AAF8AAABuAAAA
                AgAAAAAAAAABAAAAAQAAAAEAAABfAAAAZAAAAF8AAABk
                AAAAXwAAAGQAAABfAAAAZAAAAF8AAABkAAAAAAAAAAAA
                AAAAAAAAKAMAACgDAAAoAwAA4gIAACgDAADiAgAAKAMA
                AOICAABeAQAAFAAAAMIBAADCAQAAGQAAADIAAAAAAAAA
                AAAAAAAAAAAAAAAAAAAAABkAAAAUAAAAGQAAABQAAAAZ
                AAAAFAAAABkAAAAUAAAAGQAAABQAAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAwAAAP/v9DkAAAAAqgAAAAAAAAAA
                AAAAAAAAAKoAAAAyAAAASgEAAGQAbgBeAHMAcwD/////
                //8AAAAAAAAAAAEAcwAAAAAAAAAAAPAK8AqgD6APJgAA
                AAEBCQAAAAAAAAAAAFuxvz7sUfi+ZRlSPwABCABkO58/
                Ft6lvQAAAAAAAAAAAAAAAAABCAA1Xpo/jzYuPgAAAAAA
                AAAAAAAAAAABCABpb7A/SDMWPQAAAAAAAAAAAAAAAAAB
                CADlYaE/EvdYvQAAAAAAAAAAAAAAAAABAwC1FYM/wt0Z
                PgAAAAAAAAAAAAAAAAABCACGOIY/Dr4wPgAAAAAAAAAA
                AAAAAAABCACDwFo/TaHzPQAAAAAAAAAAAAAAAAIBCAAA
                AAAAAAAAAKRwjT/kFIW/1ecyPwIBAwAAAAAAAAAAAAAA
                AAAAAAAA1ecyPwEBCAAAAIA/AAAAANGR/D4fhSu/Mnd1
                P7wCKANuBFwFCgaTBtUG7QYJBwAAAAAAAAAAAAAAAAAA
                ZgHmAWsC9AJSA8wDbgRuBDYBkAEMAmsCqAL0AlIDzAM2
                AZABDAJrAqgC9AJSA8wDNgEMAjcCawKoAvQCUgPMA14B
                IANMBEwEJgJiArIC+AJmA8ADOATJBGYBxgE3AqgC9AJS
                A8wDbgRmAcYBNwKoAvQCUgPMA24EkwDyAFgB5AEVAqoD
                EwQ0BA4BHAIqAwAAAAAAAAAAAAAJB24EzAPMA8wD6ANu
                BG4ENAQqA8kEAADIACwBYAnwCigDAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAkHAQAAAAAAAAIGBlAANAEAAAAAAAAA
                AAAAAACQAZABkAGQAZABkAGQARQAVAtUCwoPUAAAAAAC
                AAAAAAAAAAAAAQAAAAAAAFCNlzwK16M7AAAAAOqymDyH
                okA9AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAABAAAA
                AAAAAKAAAAAIEAIQGgRMBOgD6APoA+gDAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAACGCyILVAsAAJABkAE4AAAAAAAA
                AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
                AAAAAAAAAAAAAAAAAAA=
                </data>
                <key>PP_PhmUseDummyBackEnd</key>
                <integer>0</integer>
                <key>PP_ToolsLogSpaceSize</key>
                <integer>524288</integer>
            </dict>

 

 

 

Luxmark : 54000

 

Geekbench V:

 

Vulkan Score 71371 Windows 10 Pro

OpenCl score 84677 Windows 10 Pro

 

Metal Score 49572 MacOS Catalina 10.15

OpenCl score 34241 MacOS Catalina 10.15

Edited September 7, 2019 by thunder72fr

[CMMChris]

New Version 2.1 released (attached in starting post). Now you can enter GPU and SoC Min and Max voltages in mV instead of having to manually multiply the values by 4.

[CMMChris]

Recommendation: Set the parameters PP_DisableDIDT=1 (Number) and PP,PP_DisableULV=0 (Number) in addition to your PowerPlay Table. This gives a significant performance boost and reduces power consumption further. The performance boost is especially noticeable in some games. For the DisableULV Parameter you need Whatevergreen since it overwrites an existing parameter.

[metacollin]

This is great, thanks for making this @CMMChris.

 

Screw undervolting though, I'm crankin' this sumbitch up as high as she'll suffer.  I'm just getting started:

 

 

Gotta improve the thermals some so I can hit 1400mV.  Then I can really crank it up.  That screen shot above is 1300mV, 2250MHz + much more aggressive fan settings.  But still using the stock air cooler, still seems stable.  \o/

Edited September 29, 2019 by metacollin

[CMMChris]

Be careful. I wouldn't do such an aggressive overclock without detailed temperature metrics on macOS.

[metacollin]

1 hour ago, CMMChris said:

Be careful. I wouldn't do such an aggressive overclock without detailed temperature metrics on macOS.

 

The Radeon VII has a hardware frequency throttle at 110 degrees C along with a hardware current/voltage throttle at 115°C, and while the true maximum temperature is not publicly known, there is definitely a good margin of thermal headroom on top of that.  And that temperature and throttle is controlled by a junction temperature sensor - in other words, a sensor (really, a network of sensors) that is integrated into the silicon itself.  This means the closed control loop is very tight (vs most prior GPUS, AMD or NVIDIA, which used sensors external to the silicon die).  The radeon VII, out of any card out there, is the one card you can just go nuts and push as hard as you want.  The worst that can happen is that the voltage is too high that it throttles prematurely and your performance will actually suffer and be a fair bit less than it would be even at normal frequencies.  There is essentially zero risk of damaging the card, especially considering the stock card defaults to running at the frequency temperature throttle point (110° C) anyway so it can keep the fan noise lower.  macOS isn't responsible for keeping the card in its SOA (safe operating area), the card is.  

 

The only risk is if you don't have the settings right, you will have stability issues under load and might have the program crash or get forcefully logged out of macOS as the GPU resets, but you won't even get a kernel panic or need to restart.  As outcomes go, that is mostly harmless.  And of course, finding your specific silicon's sweet spot can take a lot of trial and error which is a pain.  But there is no need to be overly cautious.  People have cranked their VIIs up to 1400mv+ without issue even with a stock cooler.  It just makes the card throttle itself down and you get no benefit, but if you modify the card to improve cooling, and if you got a decent bin of silicon, there are many examples of people who have gotten their Radeon VIIs chooching faster than an RTX 2080 Ti.  

 

The Radeon VII overclocks like watchmaker on crack.  

 

I'm able to monitor the junction temperature under macOS which is all one needs, and again, that's just to gauge if the card is throttling itself, you don't need to monitor it for safety.  

Edited September 29, 2019 by metacollin

[metacollin]

Lol, I am not sure if we should be using LuxMark, I don't think its results can always be trusted:

 

[iTTT]

17 hours ago, metacollin said:

Lol, I am not sure if we should be using LuxMark, I don't think its results can always be trusted:

 

 

 

 

omg.....what is your setting?

[NeXtor]

On 10/8/2019 at 8:23 AM, iTTT said:

On 10/7/2019 at 2:41 PM, metacollin said:

Lol, I am not sure if we should be using LuxMark, I don't think its results can always be trusted:

 

 

 

 

omg.....what is your setting?

 

I'm interested too

[dadi01]

On 8/25/2019 at 3:33 AM, iTTT said:

 

hi CMMChris,

 

thats a usa today protonmailvery good tool.

boot by Clover, now my R VII get 55802 scores in LuxMartk.

 

i need to make a SSDT for this PPT if i use OpenCore.

So do you know how to convert those Clover output data to SSDT format?

 

thanks so much.

omg.....what is your setting?

On 10/8/2019 at 7:23 AM, iTTT said:

 

 

 

omg.....what is your setting?

!!!

Edited October 24, 2019 by dadi01

[Thegn]

Thank you, CMMChris for releasing this! I've just moved to OpenCore and decided to put also this in test, and it works great!

[holyfield]

How to get temp meter for Radeon VII?

[dlawrence]

@CMMChris - Many thanks for releasing this tool. I plan to use it when I get a Radeon VII to replace my 1080Ti.

 

A couple questions:

 

1) I'm a bit new to this so where in Clover do parameters PP_DisableDIDT=1 (Number) and PP,PP_DisableULV=0 (Number) get set?

2) I'm planing to put an AIO water block on the card to get better performance and silence (my 1080Ti is an Aorus Waterforce Extreme so I'm used to fast and quiet). Is there anyway to set the AIO fan curves from the card's temperature, or do I just have to pick a speed and leave it?

 

Thanks for your help!

[DuIslingr]

On 9/29/2019 at 8:35 AM, metacollin said:

 

The Radeon VII has a hardware frequency throttle at 110 degrees C along with a hardware current/voltage throttle at 115°C, and while the true maximum temperature is not publicly known, there is definitely a good margin of thermal headroom on top of that.  And that temperature and throttle is controlled by a junction temperature sensor - in other words, a sensor (really, a network of sensors) that is integrated into the silicon itself.  This means the closed control loop is very tight (vs most prior GPUS, AMD or NVIDIA, which used sensors external to the silicon die).  The radeon VII, out of any card out there, is the one card you can just go nuts and push as hard as you want.  The worst that can happen is that the voltage is too high that it throttles prematurely and your performance will actually suffer and be a fair bit less than it would be even at normal frequencies.  There is essentially zero risk of damaging the card, especially considering the stock card defaults to running at the frequency temperature throttle point (110° C) anyway so it can keep the fan noise lower.  macOS isn't responsible for keeping the card in its SOA (safe operating area), the card is.  

 

The only risk is if you don't have the settings right, you will have stability issues under load and might have the program crash or get forcefully logged out of macOS as the GPU resets, but you won't even get a kernel panic or need to restart.  As outcomes go, that is mostly harmless.  And of course, finding your specific silicon's sweet spot can take a lot of trial and error which is a pain.  But there is no need to be overly cautious.  People have cranked their VIIs up to 1400mv+ without issue even with a stock cooler.  It just makes the card throttle itself down and you get no benefit, but if you modify the card to improve cooling, and if you got a decent bin of silicon, there are many examples of people who have gotten their Radeon VIIs chooching faster than an RTX 2080 Ti.  

 

The Radeon VII overclocks like watchmaker on crack.  

 

I'm able to monitor the junction temperature under macOS which is all one needs, and again, that's just to gauge if the card is throttling itself, you don't need to monitor it for safety.  

@metacollin Would you mind elaborating on what tasks the vii can bet the 2080ti in? i havent come accross any posts of users showing off benchmarks or games average fps beating a 2080ti comparatively on windows.

[CMMChris]

I added recommended additional device properties in the opening post. Those significantly enhance Geekbench results, bringing your Radeon VII closer to the Pro Vega II in the new Mac Pro.

@Teress Might be interesting for you as well.

Edited April 14, 2020 by CMMChris

[augustopaulo]

On 4/14/2020 at 1:40 PM, CMMChris said:

I added recommended additional device properties in the opening post. Those significantly enhance Geekbench results, bringing your Radeon VII closer to the Pro Vega II in the new Mac Pro.

@Teress Might be interesting for you as well.

Thanks for the update @CMMChris!

 

I've used the standard values from your latest excel.

 

Did improve my GeekBench Scores quite a bit!! Metal up by 31.4% & OpenCL by 30%!!

But the LuxMark are almost the same (51455->53245)...  Any advice to improve these ? 

 

My Clover Devices->Properties section:

Spoiler

<key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
            <dict>
                <key>@2,AAPL,boot-display</key>
                <integer>1</integer>
                <key>ATY,EFIVersion</key>
                <data>MDEuMDAuMzE4MA==</data>
                <key>CFG_NVV</key>
                <integer>2</integer>
                <key>CFG_PTPL2_CNT</key>
                <integer>16</integer>
                <key>CFG_PTPL2_MAX</key>
                <integer>300</integer>
                <key>CFG_PTPL2_MIN</key>
                <integer>90</integer>
                <key>CFG_TPS1S</key>
                <integer>1</integer>
                <key>PP_ACDCGpioDisabled</key>
                <integer>0</integer>
                <key>PP_DiDtSQPatternWidthOverride</key>
                <integer>14</integer>
                <key>PP_DiDtSQStallPatternOverride</key>
                <integer>16383</integer>
                <key>PP_DisableDIDT</key>
                <integer>0</integer>
                <key>PP_DisablePCCLimitControl</key>
                <integer>1</integer>
                <key>PP_DisablePowerContainment</key>
                <integer>1</integer>
                <key>PP_FclkGfxClkRatio</key>
                <integer>1036831949</integer>
                <key>PP_PhmSoftPowerPlayTable</key>
                <data>wgYLAALCBjQIAACkNQAAfAAJAAAAGvoA+gD6AAAAAAB2AAELAAAACQcAAG4EAADMAwAAzAMAAMwDAADoAwAAyQQAAG4EAABuBAAANAQAACoDAAAAAAAAAAAAAAAAAAAAAAAAAAAAALwCAABmAQAANgEAADYBAAA2AQAAXgEAACYCAABmAQAAZgEAAJMAAAAOAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAABDgAAAAEBAQEBAQEBAQEBAQEBAAAAAAAAAAAAAAAAAAAAAAAAHQAAAJgIAACYCAAAmAgAAAYEAACYCAAABgQAAJgIAAAGBAAAsAQAABQAAAAoCgAAKAoAAF8AAABuAAAAAgAAAAAAAAABAAAAAQAAAAEAAABfAAAAZAAAAF8AAABkAAAAXwAAAGQAAABfAAAAZAAAAF8AAABkAAAAAAAAAAAAAAAAAAAAKAMAACgDAAAoAwAA4gIAACgDAADiAgAAKAMAAOICAABeAQAAFAAAAMIBAADCAQAAGQAAADIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABkAAAAUAAAAGQAAABQAAAAZAAAAFAAAABkAAAAUAAAAGQAAABQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAwAAAP/v9DkAAAAA+gAAAAAAAAAAAAAAAAAAAPoAAAAyAAAASgEAAGQAbgBeAHMAcwD///////8AAAAAAAAAAAEAcwAAAAAAAAAAACgKIAsYEDARJgAAAAEBCQAAAAAAAAAAAFuxvz7sUfi+ZRlSPwABCABkO58/Ft6lvQAAAAAAAAAAAAAAAAABCAA1Xpo/jzYuPgAAAAAAAAAAAAAAAAABCABpb7A/SDMWPQAAAAAAAAAAAAAAAAABCADlYaE/EvdYvQAAAAAAAAAAAAAAAAABAwC1FYM/wt0ZPgAAAAAAAAAAAAAAAAABCACGOIY/Dr4wPgAAAAAAAAAAAAAAAAABCACDwFo/TaHzPQAAAAAAAAAAAAAAAAIBCAAAAAAAAAAAAKRwjT/kFIW/1ecyPwIBAwAAAAAAAAAAAAAAAAAAAAAA1ecyPwEBCAAAAIA/AAAAANGR/D4fhSu/Mnd1P7wCKANuBFwFCgaTBtUG7QYKBwAAAAAAAAAAAAAAAAAAZgHmAWsC9AJSA8wDbgRuBDYBkAEMAmsCqAL0AlIDzAM2AZABDAJrAqgC9AJSA8wDNgEMAjcCawKoAvQCUgPMA14BIANMBEwEJgJiArIC+AJmA8ADOATJBGYBxgE3AqgC9AJSA8wDbgRmAcYBNwKoAvQCUgPMA24EkwDyAFgB5AEVAqoDEwQ0BA4BHAIqAwAAAAAAAAAAAAAJB24EzAPMA8wD6ANuBG4ENAQqA8kEAADIACwBYAnwCigDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoHAQAAAAAAAAIGBlAANAEAAAAAAAAAAAAAAACQAZABkAGQAZABkAGQARQAKAooCigKXwAAAAACAAAAAAAAAAAAAQAAAAAAAFCNlzwK16M7AAAAAOqymDyHokA9AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAABAAAAAAAAAKAAAAAIEAIQGgRMBOgD6APoA+gDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACGCyILVAsAAJABkAE4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==</data>
                <key>PP_PhmUseDummyBackEnd</key>
                <integer>0</integer>
                <key>PP_WorkLoadPolicyMask</key>
                <integer>1</integer>
            </dict>

 

Edited April 16, 2020 by augustopaulo

[CMMChris]

Nothing to improve with your Luxmark scores. Almost on par with the windows drivers. The properties just fix the issue that Geekbench reports low scores.

[hackaro]

Thanks @CMMChris

 

I have this model of Radeon VII: Sapphire https://www.sapphiretech.com/en/consumer/212910140g-sapphire-radeon-vii-16g-hbm2-hdmi

 

I had a look into specifications but I cannot find all the data that you require to input in your excel spreadsheet, could you be so kind to help me? My main goal is to use it for Premiere editing and Photoshop . So I mainly need to use it for sustained periods of time up to its best performances... 

 

Thanks in advance! 

[CMMChris]

I don't get what you want to know? All Radeon VII are the same. If you have no idea about undervolting / overclocking a GPU I'd suggest not to touch it.

[hackaro]

18 hours ago, CMMChris said:

I don't get what you want to know? All Radeon VII are the same. If you have no idea about undervolting / overclocking a GPU I'd suggest not to touch it.

thanks for the reply. Yes, I don't have experience on undervaluing/OC ... that's why I was asking where I can find the correct/best values for my VII.

[CMMChris]

You have to figure them out by trying. Set VRAM clock to 1100MHz, pretty much all cards can handle that. For undervolting reduce your GPU voltage step by step. I'd suggest starting with 1050mV, then test stability for a while using Unigine Valley for example. If it's stable, reduce voltage in 5mV steps and test again. Once your card gets unstable, go up 5mV again and you should be fine.

 

With stock GPU clock of 1801MHz most Radeon VII are able to get below the 1000mV range. I can run mine on 975mV which results in low temperatures, low power consumption and silent operation.