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

RX 7800 XT doesn't go over game clock, lowering performance in 0.7.0 #452

Open
2 tasks done
IvanAtanascev opened this issue Jan 21, 2025 · 2 comments
Open
2 tasks done

Comments

@IvanAtanascev
Copy link

Checklist

  • The problem is not listed in the hardware support matrix as a known limitation. Examples of known driver-side issues are fans not turning on with a custom curve or inaccurate power limits on RDNA3.
  • I've included a debug snapshot if the issue is related to hardware configuration

Bug description

Since upgrading to 0.7.0, my 7800XT doesn't go over ~ 2130 MHz, which is close to the the card's "game clock" (can bee seen here for example). It seems to set that as "target clock" regardless of the set "Maximum GPU clock". This results in lower performance (eg. lower fps).

debug snapshot:
LACT-v0.7.0-snapshot-20250122-000245.tar.gz

Performance in Kingdom Come Deliverance's main menu, a consistent and reproducible scene:

Performance and clock speed with 0.7.0:
Image

Performance and clock speed with 0.6.0:
Image

(Ignore the RAM/VRAM usage differences, there are some background tasks that are not affecting the difference in clock speed and in game settings are the same)

The card behaves the same in other games/applications.

Screenshot from 0.7.0 (see target clock):
Image

Screenshot from 0.6.0 (target clock behaves normally):

Image

I currently use the 0.6.0 version as a workaround.

System info

- LACT version: 0.7.0-release (commit b818f39)
- GPU model: RX 7800 XT (Sapphire Pulse)
- Kernel version: 6.12.10-zen, 6.12.10, 6.12.9 (behaves the same on all of those)
- Distribution: EndeavourOS
@ilya-zlobintsev
Copy link
Owner

0.6.0 had broken pstate settings that did not get applied, which was fixed in 0.7.0. The pstates are getting reapplied because you have "performance level" on manual.
Does the issue happen if you choose "automatic" as the performance level?

@IvanAtanascev
Copy link
Author

No, the issue does not persist with "performance level" on "automatic" with 0.7.0, the card boosts as expected.

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

No branches or pull requests

2 participants