Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AutoTDP improvement / EPP setting #3392

Open
2 tasks done
AleITDE1990 opened this issue Nov 20, 2024 · 1 comment
Open
2 tasks done

AutoTDP improvement / EPP setting #3392

AleITDE1990 opened this issue Nov 20, 2024 · 1 comment
Labels

Comments

@AleITDE1990
Copy link

Rules

  • I made myself familiar with the Readme, FAQ and Troubleshooting.
  • I understand that, if insufficient information will be provided, my issue will be closed without an answer.

Is your feature request related to a problem? Please describe

I have been using AutoTDP.bat from the GPD Discord Server and your's included in the Ghelper.

I see the first one kind of separately adjusting the frequency of GPU and CPU, meeting the target at the optimal wattage for each side of the APU.

The behaviour of Ghelper's TDP seems to only control the overall TDP (and maybe the windows power mode?).

Can you please give some basic hint about how your AutoTDP works?

Describe the solution you'd like

I would also like to ask you, if you could implement an EPP slider. When I create a "power saving" profile with AutoTDP.bat from the GPD Discord, the EPP windows setting does actually become effective, as windows is not overriding it, so it would be cool having this setting accessible in you tool.

PS: what happens with the power mode setting in Ghelper's profile, when one binds that profile to a "power saving" windows power plan where power modes are actually not available?

Describe alternatives you've considered

No response

Device and Model

Rog Ally

Additional information.

No response

@seerge
Copy link
Owner

seerge commented Dec 10, 2024

@AleITDE1990 hello, sorry for a slow response - I was away :)

G-Helper's AutoTDP is very straightforward. App uses only "official" (i.e. Armoury's) power limiter to set TDP. It is the same thing as you would set power limit in AC manual mode or in G-Helper's Fans+Power.

Logic is following:

  1. It sets a default (built in into AMD driver) FPS limiter to a specific value of your choice
  2. Every 300ms it measures "actual" FPS reported by AMD driver
  3. If FPS < 90% of the limit, it instantly increases power limit on 1 watt
  4. If FPS > 95% of the limit for last ~3 seconds (i.e. it's stable) - it decreases power limit on 1 watt

It doesn't change any clocks or any other settings, because it can't same as Armoury can't.

Whole idea behind AutoTDP here is to let you drop power consumption a bit for existing FPS limiter, without sacrificing performance.


I would also like to ask you, if you could implement an EPP slider. When I create a "power saving" profile with AutoTDP.bat from the GPD Discord, the EPP windows setting does actually become effective, as windows is not overriding it, so it would be cool having this setting accessible in you tool.

"EPP slider" (i.e. Windows Power Mode) is already in the app under Fans+Power. I usually keep it on Best Battery Efficiency or Balanced, then windows won't run CPU on maximum clocks unless really needed. When you change it - it immediately reflects in windows settings.

PS: what happens with the power mode setting in Ghelper's profile, when one binds that profile to a "power saving" windows power plan where power modes are actually not available?

If you use custom windows power plan (not power mode!), that locks power mode to specific setting, then no matter where you try to change power mode (in windows settings or in G-Helper) it won't have any effect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants