Check out our Monthly Survey Page to see what our users are running.

DiRT Rally tested on R7 370 and an A10-9600p APU

By - | Views: 27,066
I might be just a bit late with these numbers but I figured I’d share them nonetheless. Let’s check out how well DiRT Rally runs on my Radeon hardware!

To start out let’s go over the system requirements for DiRT Rally and compare them to the systems I will be using to benchmark the game.

The minimum CPU requirements are an i3-4130T 2.90GHz or an AMD FX6300 with i5-6500 3.20GHz being recommended. My main rig has an i5-2500K clocked at 3.3GHz, which meets the minimums quite easily. My laptop, which I am also using for benchmarking as the low-spec system, has an A10-9600p at 2.4GHz which likely falls below the minimum requirements.

When it comes to GPU requirements, an R7 270 is placed as the minimum along with the 650 Ti and the Intel Iris Pro 6200 and a 970 is recommended. My main system still uses the R7 370 4G which is close to the 270 in terms of performance, considering it is practically the same chip with slightly higher clock speeds. The laptop uses the APU’s built-in graphics chip which is marked as an R5 (320 stream processors at 720MHz). The APU is significantly slower than an R9 270. Both systems have the minimum required amount of RAM (8GB) with the main system using 1333MHz DDR3 memory while the laptop has 1866MHz DDR4.

Both systems run Antergos 64-bit with kernel 4.9.11 and Mesa 17.0.0.

Now that that’s done, let’s dive deep into the world of numbers and framerates!


As you can see, my main gaming system dealt with DiRT Rally quite well. The game remained playable all the way from Ultra Low to Ultra. At Ultra Low the average framerate was a 197 FPS and the game only dropped as low as 143 FPS. At Medium settings the minimum framerate was still at 59 FPS, meaning the framerate was as smooth as it can be all the time when viewed on a 60Hz monitor. On High and Ultra the minimum framerate dropped to the 40s but averages were still on the healthier side of 60 FPS.


On the APU things weren’t going too smoothly anymore. At 1080p only Ultra Low could be considered playable, with the average being at 43 FPS and minimum at 35 FPS. Going anywhere above that resulted in the minimums and averages to drop below 20 FPS. You could probably fiddle with the settings to get a stable-ish 30 FPS with a combination of Ultra Low and Low settings at 1080p. Considering this laptop of mine isn’t really a gaming beast, I’d say this is acceptable performance.


Dropping the resolution down to 720p definitely helped the APU pump out some additional frames, but going above Ultra Low still resulted in an experience I would no longer call playable. However, tweaking with the advanced settings should allow for a slightly shinier graphics at 720p than at 1080p. Alternatively you could just stick to Ultra Low and you would get an experience I would call fully playable, with the framerate being between 49 and 83 FPS.

Also worth noting is that there were graphical glitches with the A10-9600p when graphics were set to Low or above. The glitches were fairly minor however, the tape fence along the track seemed to blink in and out but nothing else seemed to be affected. I'm not sure what caused this but considering it didn't appear on my R7 370 it's possibly linked to the amdgpu kernel driver, which is what my APU uses.

In conclusion, DiRT Rally performs pretty damn well on Linux and I don’t have anything to complain about when it comes to performance. Keep in mind that while I did include my laptop into the testing, I did not expect particularly great results from it to begin with and I’m actually quite happy with how things turned out with the APU.

Have you tried out DiRT Rally on your system? Make sure to share your performance numbers in the comments! Article taken from
We do often include affiliate links to earn us some pennies. We are currently affiliated with GOG and Humble Store. See more here.
About the author -
author picture
I'm a Linux gamer from Finland. I like reading, long walks on the beach, dying repeatedly in roguelikes and ripping and tearing in FPS games. I also sometimes write code and sometimes that includes hobbyist game development.
See more from me
The comments on this article are closed.
Page: «2/2
  Go to:

saildata 5 Mar, 2017
View PC info
  • Supporter
Quoting: saildata
Quoting: RussianNeuroMancerSwitching CPU governor from ondemand to performance could be very useful for running games on APU.

Both good points.

@meggerman I noticed over 55% frame count reduction with no visual improvement; so all loss no gain.

Not sure if it just scales really well or what. For MSAA I haven't even tried lower yet,

I usually just alter one variable at a time so it's easier to attribute causality. I'll check it out and see how it does (I'm sure it can only improve with less computation per frame!)

Oh, and yes the rest of the system is Gnome shell at 2160p.

@RussianNeuroMancer modern chips don't really see much benefit from governor changes, I usually stick with p-state for thermal sanity but totally agree that there could be some upside to performance.

I also wanted to test disabling the new default Nvidia threads config, that's one that can sometimes be huge gains or losses depending on the code. Usually it's gains but with these ports you never know what the secret sauce will be.

Overall, I'm a happy camper at over 80fps.. refresh is 60 so it's all bonus at this point.


I've tested a few changes and wanted to let others know in case they are looking for performance improvements.

Changing from MSAAx8 to MSAAx4 (governor=p-state powersave): 21,811 frames (+21.1% increase) Min/Max/Avg fps: 83.8/127.2/106.2

Changing from powersave to performance governor (MSAAx4): 21,260 frames (-2.5% decrease) Min/Max/Avg fps: 83.1/128.0/105.3

(someone asked about RAM) 64GB DDR4 @ 2400 MHz

The last test I want to run is moving the game install to my other/spare NVMe drive in case there is any iowait (NVMe usually has 0% iowait, but just testing... :)

Tested the separate drive theory.. all else equal (MSAAx4, p-state powersave) showed under 1% improvement in frame count which is probably within margin of error. 22,000 frames (+0.9% increase) Min/Max/Avg fps: 85.0/131.3/107.1

Last edited by saildata on 6 March 2017 at 7:26 am UTC
Samsai 6 Mar, 2017
Quoting: Dea1993woow
i've a laptop with an APU A10 8700p (very similar to the A10 9600p).
my APU has 15W tdp (the version with 35TDP, is a lot more powerful), how many TDP has the 9600p that you have tested?
have you tested with DDR3 or DDR4??? what is the frequency of the ram?
for the integrated APU's GPU, the ram frequency is really important for performance.
you must give us more information
RAM frequencies were mentioned in the article. It's running 1866 MHz DDR4 and the TDP of this APU is 15W, which I think is the default for a 9600p.

And when it comes to DIMM amount, I'm pretty sure there's two sticks in there running in dual-channel. This laptop's an absolute bitch to get to the innards though, so verifying that isn't particularly easy. And for those interested in the model, this is an HP Notebook 15, the APU variant.
saildata 6 Mar, 2017
View PC info
  • Supporter
Quoting: Dea1993And when it comes to DIMM amount, I'm pretty sure there's two sticks in there running in dual-channel. This laptop's an absolute bitch to get to the innards though, so verifying that isn't particularly easy. And for those interested in the model, this is an HP Notebook 15, the APU variant.

Check out lshw (list hardware)

To get the detailed memory info, sudo lshw -c memory
While you're here, please consider supporting GamingOnLinux on:

Patreon, Liberapay or PayPal Donation.

This ensures all of our main content remains totally free for everyone with no article paywalls. We also don't have tons of adverts, there's also no tracking and we respect your privacy. Just good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.