I don't quite understand this issue. My Global profile is set at it's default..power saving. The game profiles is where I set the features I want for that particular game. Honestly, I assumed everyone did it this way. I have no reason to use the full power of my graphics card to surf the web.
Well that's an understandable sentiment/approach. There's not exactly a tutorial on per game profiles readily available via the drivers or any built in help system, so I don't expect everyone's going to exactly catch on to that. It may be intended-use. That's not been made clear. And on top of that, I doubt that simple web browsing is going to get past p-state 3 on the above mentioned GPUs. It's kind of a moot point whether you've got a tuned profile or not when browsing the web - the power savings would be negligible ... unless you got this itching problem where you've got a custom profile and your fans are roaring while browsing the web because the zero rpm feature is broken on said profiles.
Otherwise, I consider global wattman profiles more useful than individual ones - there might be an outlier, but that's what I assume the individual wattman profiles are for. I don't use them personally. I do use the game profiles in their generic form, but only because there's no global radeon chill range.
I found it about pointless to make wattman changes individually. Forgive me if this is something they recently fixed and I have missed it. But I find that as soon as I make changes globally after changing the individual profiles it overrides my individual settings. So for me other than the graphics settings I too leave the wattman settings alone in the individual settings. You spend a bunch of time making the individual settings to not have the driver honor what you set anyway. I fully realize this feature may or may not work for some and not others. The drivers have long been flaky like that. It would be nice to be able to use it as kingfish is using it. On my RX 580 you can't run global defaults as you would not be able to run anything. The card doesn't work at defaults.
the power savings would be negligible ...
wrong point ... more importantly reducing fans' bearing wear when off hence the fan stays smooth/quiet for much longer
Well, this issue has cropped up again for 19.5.2, except the fix is a bit different this time around. For vega 64, it seems..
<FEATURE ID="18" Enabled="True">
<STATE ID="0" Enabled="False" Value="0"/>
..will set the manual curves + zero rpm mode to enabled. This is different from the last xml profile edit. I don't actually know if the manual fan curves are working however, I haven't tested it, only the feature availability. Saving the profile, over-writes the edit, so the edit has to be made again. This is actually a functional regression from previous hack+fix.
Any one with a zero-rpm mode issues can save their profile and custom fan curves as one file, then save this again, except with the zero rpm mode toggled on. Comparing the files side by side should reveal which feature ID zero rpm mode is by the: Enabled True/False variable.
Edits: the application of the edited profile might be finicky. On 19.6.1 my system boots fine but wattman crashes on previously stable settings on boot. Reapplying the profile works, but now I'm in the bucket of people who are dealing with inconsistent wattman behaviour on startup. The XML edit may be to blame, I'll have to hash that out some other time though.
I understand if you treat it like a subjective matter but it's probably brought on by the illusion of improving something that you in fact are only using the way it's ment to be. In other words, it's the opposite of subjective or personal.
Cooling carefully and meticulously engineered technology is calculated to an unknown amount of decimals and there is benefits (ignore sound for a moment) in following any such projected curve, in proportion to the energy required to cool, the accumulative wattage over time, or joule and a large amount of variables that can be taken into account;
Depending on the environment (presuming it's controlled within reasonable margins).
This is not actually that hard to make a semi scientific (since a single citizen likely lack the funds to observe and confirm the outcome, en masse) estimate but even without one it shouldn't be interpreted as subjective or motivated by noise. If you are sincerely attempting to eliminate noise, a logical approach to reaching that goal without seriously mishandle your hardware would be to include your graphic unit with the systems (CPU) liquid-based cooler.
I am myself contemplating sporting a bracket with kit to extend my Fractal Design Celsius S36 to include my Vega 64 with my Ryzen 7 cooling.
I just wanted to make sure that our difference of attitude toward these matters were pointed out because there's a generational gap between those of us sporting C64 and Amiga compute and AMD when they released their first 64-bit CPU, and the generation that grew up with tablets, automated mobile phone units with made up colours and absolutely no freedom of choice and therefor no urgency of there being any risk involved. There is, by having an overly casual relationship with technology.
Sorry if I digressed from topic.
I think we're on thre same page.
To clarify my statement [ your choice of ] a fan curve is subjective - I'm not dissenting against factory curves of engineering samples or bone stock.
The fact is, ( on that version of the drivers and several since then ) - popping out of factory factory default and initiating a custom curve results in a completely garbage fan curve ( or more like a line ). This data it pulls from the ether to make that curve is not an accurate representation of the actual factory fan curve (for whatever reason).
Can only set xmls ID 18 to true to fix this and have it permanently on. It will kick in under 48 degrees celcius and turn fans on at 55. Wish amd development team at radeon would get fired and put some of me and other guys in. These radeon settings are jokes. We need our mips back aka prerender. Better dx9 support. On new cards. Make radeon pro PRO not amateur. To not fix a simple switch based on xml and one button graphic connected to it (switch is already existing) is a fricking joke to me.... There are developpers and designers and coders and builders and very smart techies around (NO NOT IT IT IS FOR SCHOLAR NUBS), real underground techies. LISA you need to work more and get the filth out as you brought amd back on the map get rid of the ones who took it off and stay lazy these are the same mistakes as in the past with people probably the same developpers for years! Simple things...... Amd simple things..... Stay teched not hyped by 80% that now suddenly became aware of a technical world and never did before the year 2010.
Tech world is now lost in dummies...... I hear you other 20% that get ignored and overrules by false information and practices! Stay strong!
AMD, I missed you since 2006. Welcome back. Been green and blue for years but my heart is always red. We know what amd did for the pc/cpu/gpu world. Not Nvidia not intel.... they forgot...... Who r the real deal......
Ryzens architecture and ipc blows away anything with the same specs and frequency. When i compare that vs a blue teams 1ghz higher clocked ipc and i see ryzen tickle the insane higher clocked blue processor,.... I get nerdgasms... Very proud of ryzen. Same for polaris. Very well done. Highly underated due bias looks in buyers and reviews. I dont go all AMD for no reason coming from all blue. Feels like bulldozer never excisted...
Which is another point. Focus on desktop more than mining/hash/server/workstation. I mean im proud but.... It is easy to see that polaris is a mining focussed card not a gaming (even if it is a gaming card among the best!). Just like it is as easy to see that ryzen is a server/workstation repolished to be able to compete for desktop qualities.
I mean you caNt fool me.... Let's just be honest.