Why is my RX 9060 XT slower on Arch than on Windows?

November 20, 2026 4 answers
Asked by DpadWiggle_6K

I'm comparing the same game on Arch and Windows at 1080p with an RX 9060 XT and a Ryzen 7 5700X3D. Arch gets around 60 to 70 fps with GPU usage below 100 percent. Windows runs faster, especially with upscaling.

I've tried the performance CPU governor, enabled Resizable BAR and 4G decoding, changed the GPU power profile, and tested both Wayland and X11. What else should I check?

Answers

staminaTickRate

The small improvement from upscaling and the GPU sitting below full utilization suggest looking for a CPU limit or frame cap. Neither reading proves it on its own, though. Overall CPU usage can look modest while one busy thread holds the game back.

Use a performance overlay to watch individual CPU cores, GPU load, clocks and frame times during the same repeatable section. Check the game's frame limiter, vertical sync and any desktop compositor settings too. The CPU hitting 100 percent while paused could be a separate menu behavior, so I wouldn't diagnose from that alone.

Reply to this answer
QTEprompt~NotYet

Make sure the comparison really is like for like. Match the resolution, graphics preset, ray tracing, upscaling mode and frame generation settings. Also check whether the Windows number includes generated frames, since those aren't directly comparable to native rendering fps.

Run the same scene after shaders have had a chance to compile. A benchmark from a different area or a first run with shader compilation can muddy the result quite a bit.

P8whiffPunish_2L:

Frame times are worth comparing alongside average fps. Shader compilation may show up more clearly as stutter than as a large average performance drop.

Reply to this answer
GBAreadAhead_5D

Check the actual graphics stack, not just whether packages are installed. On Arch, the AMD driver is split across the kernel, firmware and Mesa. For a Windows game, the Vulkan driver and the compatibility layer version matter too.

Update the system and reboot, then verify that the game is using the AMD Vulkan driver rather than a software renderer. Try another compatibility layer version as a controlled test. Change one thing at a time so you can tell what helped.

GBCspriteDMA_7L:

For a 32-bit game or component, the matching 32-bit Vulkan packages may also be needed. Which packages matter depends on how the game is launched.

Reply to this answer
coinopTicketLedger

I'd leave the power tweaks alone for a moment and check clocks and temperatures under load. The performance governor and high GPU profile don't guarantee either chip is maintaining the expected clocks. Thermal or power limits could still be relevant.

If clocks look normal, try another game or benchmark. That helps narrow down whether this is specific to the game and its compatibility layer or a broader system issue.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions