mesa
mesa copied to clipboard
daniel-schuermann
Benchmarks results
Just for visibility, this can be a meta issue for referencing various posted benchmarks.
I used this project on the implementation of my bachelor's thesis, which is about ray tracing volumetric models with Vulkan (https://github.com/Snektron/Xenodon). Im happy to report that performance more than doubles (on the single dataset i've tested). From some viewing angles my RX 580 even performs better than a GTX Titan X (Pascal)! Amazing work, im very impressed.
The output of my benchmark can be found here: https://gist.github.com/Snektron/0c601b89cc09bcfe29a93734d47d3482
with Middle Earth Shadow of War, medium settings (DXVK):
71 fps with RADV Mesa 19.1.1 73 fps with Mesa-aco master.
Shadow of The Tomb Raider, medium settings (DXVK):
39 fps AMDVLK git from last week 32 fps RADV, Mesa 19.1.1 34 fps RADV/ACO master git.
Just what version of Mesa should we compare ACO against? Is it 19.1.X or 19.2-git ?
@SR-dude you can disable ACO by setting RADV_PERFTEST=llvm without changing your Mesa build.
My question was when did ACO fork? 19.1 or 19.2? For clean performance testing, it would be unfair to compare ACO against an old mesa version.
Quake Champion, Ultra presets, render scale 100% (DXVK), on a rx580:
with ACO:
with RADV_PERFTEST=llvm :
Also an issue with this game is heavy stutters when first time encountering a shader:
ACO in the menu when loading bots with random skin (longer frees 1.2 seconds):
with RADV_PERFTEST=llvm (longer frees 2.4 seconds):
The Talos Principle, Ultra settings: 69.1 fps with ACO 66.3 fps with RADV_PERFTEST=llvm
Middle-Earth: Shadow of War, mix of high-ultra, 3440x1440, low filters. Using the in-game benchmark. Each test ran 4 times since I noticed performance would increase after each run. GPU is a Vega 64, Proton 4.2-9.
llvm: 82fps aco: 85fps
The Rise of the Tomb Raider benchmark: with and without ACO 47 fps at 1080p medium quality settings. Using RX560 2GB, Ryzen 5 1600 and Debian Sid Xfce. When you install ACO mesa to /usr/local to not to mess your current mesa, add the following lines into SteamLibrary/steamapps/common/Rise of the Tomb Raider/config/extra-environment.sh: LIBGL_DRIVERS_PATH="/usr/local/lib/x86_64-linux-gnu:/usr/local/lib/x86_64-linux-gnu/dri/" LD_LIBRARY_PATH="/usr/local/lib/x86_64-linux-gnu:${LD_LIBRARY_PATH}" VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/radeon_icd.x86_64.json
If you want to see the ACO is in use warning message, add --log-to-file to the launch parameters with the Steam client. The log file is in the ~/.local/share/feral-interactive/Rise of the Tomb Raider/ folder.
ACO is currently based on 6cc213b.
@pendingchaos @daniel-schuermann: Can you please rebase on the recent Mesa master, to make use of the latest fix for llvm 9?
Another RoTTR benchmark (built in benchmark, Vega 56, 1440p, mostly high settings):
LLVM git (with LLVM9 fix): 85.53 fps ACO git: 99.33 fps RADV_PERFTEST=llvm (with bugged graphics): 92.67 fps
I'm not sure if my build is slower for some reason, or if the bugged build is faster due to missing effects. But looks to be 7-16% increase from ACO over the LLVM builds.
Star Citizen with Steam Remote Play:
llvm: 40 - 55 fps Aco: 45 - 60 fps
Ryzen 2700X, soon to be tested with Ryzen 3900X
more importantly, shader stutter is cut in half, tho the game can still die, if you have to compile a heavy one. Correction: the game does not die, it only hangs for 20 seconds, but then you are done with it. Happened two times on the most graphic intense places. But after that with aco shader the game becomes playable. Barely no stuttering at all. :)
https://www.youtube.com/watch?v=z7_kU6CQpvI shitty fps due to steam remote play
From Vulkan examples and demos https://github.com/SaschaWillems/Vulkan Ubuntu 19.04 Kernel 5.1.16, Ryzen 3 1200 + RX 550
Compute Raytracing RADV_PERFTEST=llvm 54fps ACO 112fps
Compute Cloth RADV_PERFTEST=llvm 720-735fps ACO 620-650
A few others have seen minor fps increases and decreases. Haven't tested all of them.
Edit 1: Bloodstained Ritual of the Night GOG, WineHQ staging, DXVK 1.2.3 1920x1080 all Epic settings, standing still at very first room RADV_PERFTEST=llvm 76fps ACO 79fps
Nier: Automata (4K, AA off, blur off, Vega 56) opening shmup sequence until it shifts horizontal. Approximate numbers (just monitoring DXVK_HUD while playing). The averages are likely even higher for ACO, since the game is limited to 60 fps. LLVM rarely gets near 60 fps.
ACO: AVG = 57 fps, MIN = 45 fps LLVM: AVG = 44 fps, MIN = 37 fps
@pendingchaos @daniel-schuermann: Can you please rebase on the recent Mesa master, to make use of the latest fix for llvm 9?
We will definitely do so in the next couple of days, but it needs some changes to ACO, which is why we didn't do it yet.
Star Citizen with Steam Remote Play: Correction: the game does not die, it only hangs for 20 seconds, but then you are done with it. Happened two times on the most graphic intense places. But after that with aco shader the game becomes playable. Barely no stuttering at all. :)
Thx, could you elaborate if this extreme freezes also happen with llvm with an empty shader cache? 20s for a single shader sounds a bit crazy even if it hits some worst cases in our algorithms.
Star Citizen with Steam Remote Play: Correction: the game does not die, it only hangs for 20 seconds, but then you are done with it. Happened two times on the most graphic intense places. But after that with aco shader the game becomes playable. Barely no stuttering at all. :)
Thx, could you elaborate if this extreme freezes also happen with llvm with an empty shader cache? 20s for a single shader sounds a bit crazy even if it hits some worst cases in our algorithms.
They do but not that long, but more often. It is the moment when you go from Riker Memorial Station by train to Area 18, just before the train will go around the last corner. LLVM does have lots of heavy stuttering here, sometimes 5 - 10 seconds long. ACO has way less stuttering just that one bigtime one. It took so long, I was already on the train going the way back, when it finished.
If I can help you with debugging, let me know what variables to set.
Now that Dishonored 2 is fixed in the latest release I did a quick and simple test where I compared the performance of ACO to that of LLVM in a certain scene during the training level (Standing on the edge of the roof you spawn on during the stealth training while looking at the generator). This game profits lots from ACO.
ACO: 79fps LLVM: 70fps
Also the average FPS while playing through the game is also significantly better, LLVM gets 60-80fps while ACO gets 70-90. Very impressive.
The game however is still a unplayable stuttery laggy mess while playing through a level for the first time.
I have tried some games at 2560x1600 maxed settings on a Vega 56 nano, and have seen about 1-3fps gain across the board on the games I have tried so far. There is also a notable reduction in stuttering in certain games (that is hard to measure but you see it), especially in games like Tekken 7 and Hellblade.
Hellblade ACO: 55.4 LLVM: 54.1
A Plague Tale ACO: 50.1 LLVM: 48.8
The Surge ACO: 83.5 LLVM: 82.5
Witch Hunt ACO: 30.2 LLVM: 27.2
Redout ACO: 101.0 LLVM: 99.9
I have not encountered any games yet that performed worse or had graphical issues or crashes.
EDIT: System Specs: system_info.txt
1080p Dark souls 3 Intel HD 4800MQ, AMD WX 7100. ACO doesn't seem to add much to the average FPS but I noticed something very fun after bringing up my dual boot. ACO/ LLVM w/ Mesa: 46-47 FPS Windows 10: 40 FPS
Just FYI, mesa-aco is still hanging when built with latest llvm 9 and run with RADV_PERFTEST=llvm.
We are actually waiting on https://github.com/daniel-schuermann/mesa/issues/64 to be sure to not introduce new regressions when updating.
@daniel-schuermann: I see it was fixed! I'm not sure how to track rebases, since the log shows latest commits. Can you please post here once you rebase on newest Mesa? Thanks!
@shmerl: it's not the very newest mesa, because we like to have a bit of testing ourselves, but it's done :) Using RADV_PERFTEST=llvm shouldn't expose any rtld bugs anymore on master.
Supraland:
llvm:
aco:
Not much of a difference, and frametimes jumping all over the place in both cases. Something is off with Unreal Engine Vulkan usage.
Elite Dangerous Ryzen 1800X and Vega 64 running on Manjaro testing (5.2.1 kernel), installed mesa-aco-git 19.2.0_devel.113859.5031ab774a6-1 from the AUR.
Tested: fuel scooping, planetary landings, and docking at Explorer's Anchorage near Sagittarius A. Explorer's anchorage has a moderate amount of traffic.
Running at 3840x2160 with Variable Refresh set to true in the xorg conf.
Comparing to Windows version, running natively I get 60fps (monitor refresh cap, didn't test vsync off) and 60fps under Proton 4.2-9 and RADV-ACO in space while fuel scooping.
Docking at Explorer's Anchorage framerates average 52 natively in Windows, RADV-ACO averages 49.
Planetary Landing, went to Stuemeae FG-Y d7561 ABCD 1 a and picked random spots to land, averaged 45fps natively in Windows, RADV-ACO averages 43.
Mesa 19.2 and ACO appears to have reduced the performance delta from 15% to 5% since I last compared framerates 3 months ago.
Rise of the Tomb Raider - Ryzen 1800X and Vega64, 3840x2160, AF set to 8x, AO on, textures very high, all other options turned up to max detail. Using mesa-aco-git 19.2.0_devel.113859.5031ab774a6-1
Windows 10 DX12 Mountain Peak 56.07 (min: 19.14, max: 127.74) Syria 49.15 (min: 30.46, max: 66.88) Geothermal Valley 51.51 (min: 35.65, max: 60.86) Overall 52.42
Manjaro using Feral Vulkan port: Mountain Peak 53.86 (min: 33.81, max: 80.81) Syria 50.05 (min: 24.37, max: 82.56) Geothermal Valley 49.31 (min: 35.10, max 73.41) Overall 51.13
You folks in the Valve Open Source Graphics Group are wonderful, this is the best performance I've seen my Vega 64 pull out yet. This is a great improvement not just for DXVK games, but across the board. Thank you very much, as well as the outstanding Mesa devs. If this isn't "Fine Wine" idk what is.