| Bug ID | 108330 |
|---|---|
| Summary | WarThunder game performance killed after Ryzen optimisations |
| Product | Mesa |
| Version | git |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/radeonsi |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | acelists@atlas.sk |
| QA Contact | dri-devel@lists.freedesktop.org |
After the recent optimisation of radeonsi for Ryzen CPUs (appa= rently change in thread management distributing them to CPU cores), the performance of the WarThunder game dived radically. Normally it was 40-60FPS. After the change it appears OK when in plain fiel= ds, but when moving the vehicle into a more intensive area, where shots are fir= ed or other player vehicles are around, the FPS drops to 0-10 with really noticeable freezes and stuttering. This was never the case before the chang= e, The GPU is Radeon RX 560 (4GB memory). The CPU is AMD Threadripper 1920x (12 cores/24 threads) so it may be one wh= ere the optimisations are applied. Are Threadripper CCX/core layout properly recognized by the patch for Ryzen? Before the patch I noticed, the speed of the game can be visibly negatively affected if other tasks are running on the CPU. So I always run the game wi= th no other CPU heavy tasks running. The report is also with no other tasks. It may be the change of thread scheduling from the patch has now invoked the core/thread load scenario the game is sensitive to. I run Mesa from git so I noticed this problem when it was merged. Now running on Mesa 18.2.2 stable and the problem is not there.
| What | Removed | Added |
|---|---|---|
| Blocks | 108530 |
| What | Removed | Added |
|---|---|---|
| CC | kenneth@whitecape.org, maraeo@gmail.com |
Just to double-check, you're talking about commit 28e542dcdbb "gallium/u_threaded: increase batch size to increase performance" Marek, Ken do you have any suggestions?
No, I assume it was https://cgit.freedesktop.org/mesa/mesa/commit= /?id=3D25ffb8401638a07d774cfc68ab6afc7d27780dd8 as that one was reported at https://www.phoronix.com/scan.php?page=3Dnews_item&= amp;px=3DRadeonSI-Zen-Tuning-Merged and that is the tie the problem started.
Could we get a patch like https://lists.freedesktop.org/archives/mesa-dev/2018-November/20= 8785.html so that I can try to turn off the L3 cache thread pinning for this game?
(In reply to aceman from comment #3) > Could we get a patch like > https://lists.freedesktop.org/archives/mesa-dev/2018-Novemb= er/208785.html so > that I can try to turn off the L3 cache thread pinning for this game?<= /span > Just use that patch and add an entry for your game like this: > + <application name=3D"Blender&qu= ot; executable=3D"blender"> > + <option name=3D"disable_L3_thread_pinning" v= alue=3D"true"/> > + </application> > + replace blender with the name and executable of your app.
Good idea:) I did that, but it seems to not help in any way. How do I check if the option is picked up? Why is drirc now called 00-mesa-defaults.conf ? Where should it be put in /= etc ?
So strangely the patch didn't work, but updating mesa today (p= resents itself as 19.0.0), containing the commit https://cgit.freedesktop.org/mesa/mesa/commit= /?id=3De0c7114eb3c19d4c2653f661698a6baa3bc9bedf FIXES the problem immediately. The current mesa is even faster than 18.2.x that I had to use while this problem was existing.
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | FIXED |
As pointed out L3 thread pinning is disabled now. With the com= mit present in both master and 18.3.0-rc3.
Thanks. And the new version of the patch, https://cgit.freedesktop.org/mesa/mesa/commit= /?id=3Dbc5adc27b5e52d27eca6a61ad1e049b160570c98 seems to work OK. WarThunder has mesa_glthread=3Dtrue in drirc.