FR: Support for Energy Performance Preference (EPP) - the new 'governor' for AMD CPUs. #71
Comments
|
Seems pretty easy to implement, but I'm not sure if there's a way to get the current numeric value. Can you run |
That doesn't get it but I use this: (They're all set to performance right now) Or set them with |
|
BTW These are in a strange order, from fastest to most energy efficient/slowest it goes performance > balance_performance > default > balance_power > power |
|
Implemented with ba014a7 |
|
I'm afraid it doesn't quite work right.... I tried it and set everything to Power preference, and this is what I got: This is a 12 core 24 thread CPU and it's set the preference for the number of threads that I have cores, but missed the second half, so the first 6 cores of the 12 got set but half of them didn't. |
|
Also, I notice that if I change it somewhere else, I have to exit tuxclocker's GUI and restart it, so that it will show the change. This might be a separate issue, I'm not sure if tuxclocker usually updates when changes are made elsewhere (like if I use nvidia-smi or something I don't know if it updates in tuxclocker's GUI?) |
Sounds like this should affect other CPU settings like governor setting as well. Run these commands to get a better idea of what's happening:
|
|
Also, how many cpuN lines does |
It doesn't, and the current value is only checked at launch |
|
Hi @Lurkki14 Sorry I took so long to reply, I didn't get a notification for your replies. Weird. I just popped by to message you and saw this waiting for me. Sorry about that! To answer your questions: I included 4 of the sections I know you said one should be enough but I found it interesting that it get's up to core id=13 out of cores=12, and thought it may be relevant. Thanks again for adding this :) I imagine you'll be able to get it to work without problems. |
|
https://github.com/Lurkki14/tuxclocker/tree/threadfix attempted fix in this branch |
|
Thanks! It works! :)
The core sorting is a little bit weird but it's the same in the shell so I'm used to it. BTW @tujhen package which I branched to test this, was super broken tho :/ fails on the missing icon and desktop file, service file generates errors because it has no downloadable source set, version is not set, files are uploaded which should be downloaded by the service.... I think it needs a little bit of a cleanup my dude :) |
|
Opened separate issue for the sorting issue #76 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current CPU overclocking features include the ability to change governor, which is the traditional way to deal with that kind of requirement, but for modern AMD CPUs, where the
amd-pstate-eppdriver is in use (which is the default since recent kernel versions), there are only two governors, performance and powersave. These are supported by tuxclocker:But rather than changing governor, when using the AMD EPP driver, the better way to have the CPU performance change is not to change the governor, but to change the Energy Performance Preference. This EPP feature is also supported by some Intel CPUs, there's a tool for it called
x86_energy_perf_policyand it's also supported bycpupower(iecpupower set --perf-bias 0) but those only support Intel CPUs for now. EPP can also be changed on AMD CPUs using tools likecorefreq-cli, or for example, the DE's power management tools, for example KDE's 'Battery' plasma widget has a nice slider for it:Using the Performance EPP preference with the
powersavegovernor gets you the same performance as using the Performance governor, but using that same 'powersave' governor with the EPP preference set to Energy, the CPU will be far more energy-efficient. So, the advisable way to handle what we used to do by changing governor, with new AMD CPUs using the new driver, is to just leave the governor as it is, and change EPP instead.So that's why it would be cool if tuxclocker supported it :)
The text was updated successfully, but these errors were encountered: