Radeon Gallium3D Still Long Shot From Catalyst
Phoronix: Radeon Gallium3D Still Long Shot From Catalyst
Following recent advancements in the open-source Radeon Linux driver like 2D color tiling support, I've carried out some new benchmarks of the open-source Radeon Gallium3D driver compared to AMD's official Catalyst driver. This time around, the open-source driver is seeing tests against AMD's binary blob when various performance-optimizing tweaks are enabled to see where the performance stands today.
Thanks for the updated comparison Michael!
I know I am maybe asking too much. But I think it would be quite interesting to see traces(apitrace supports CPU profiling) of the benchmarks for the very slow results at least, just to get a better idea where the binary drivers are faster.
Btw I think one could actually use api traces of games as benchmarks. This would additionally ensure that the same call paths are executed, no fall-backs or workarounds for specific hardware taken.
Can someone point me to a tutorial of some sort on how to get the latest mesa stuff running next to catalyst. Are phoronix test setups documented?
Michael, where is the Doom3 test?
I still consider this wide gap between r600g and Catalyst on higher res/quality to be due to still missing optimizing shader compiler.
At lower res/quality GPU can keep with unoptimized shaders, but with lots of pixels the game changes. What happened with Vadim Girlin's initiative on that?
nvidia had hardware scheduler so far, and that is the reason for better nouveau speed, event unsupported by nvidia, but now with kepler, they go AMD route, with software scheduler in the driver ( at least thats what anandtech says ).
Originally Posted by log0
* Use a distribution like gentoo that actually allows several libGL implementations to exist on your system. You need to load modules manually, and switch between two xorg.conf (i.e. forget XDM), but it can work.
* Just install a separate OS on a different partition. Maybe play around with UnionFS to save space.
* Try to manually install both on an unsupported system, go crazy over the conflicts that arise, eventually bork your system and reinstall.
Honestly, if you have to ask how to do it, go with option 2. It's safer.
Debian has glx-alternative packages for allowing binary/open-source GPU drivers to coexist.
Yeah, catalyst sure does have a long way to go before it has the utility and openness of radeon-g3d.
Regrettably, this doesn't work. When you profile an apitrace replay, you find that a huge portion of the profile is simply apitrace parsing the multigigabyte trace file.
Originally Posted by log0
Hmm, I've got a couple traces from games and my own stuff(20-70fps, 100-400MB). And they take about the same time.
Originally Posted by mattst88
Just did a quick run with vdrift about 2min, 130MB trace. Frame rate without tracing is about 22fps, with tracing 17fps, retracing 15fps(68% of original fps). Are my results atypical?
As I see it, the slowdown would be the same for all benchmarked cards and we are interested in the relative performance only.
Buy lots of RAM and store the apitrace in a Snappy or LZ4-compressed ramdisk That should provide for a faster load time for the apitrace...