X-Git-Url: http://git.nikiroo.be/?p=gofetch.git;a=blobdiff_plain;f=test%2Fexpected%2FREDDIT%2F2018-10-09_15-00_RADV_vs__AMDVLK_vs__Rad.html;fp=test%2Fexpected%2FREDDIT%2F2018-10-09_15-00_RADV_vs__AMDVLK_vs__Rad.html;h=dd99bce3d410db86ea5b4e8d3feff5296cc2a3c3;hp=0000000000000000000000000000000000000000;hb=254d5bc320fa106f9d0a05c1e32a09adda6f82e0;hpb=7273fd5890478d6ec1f3c566e0c5e4640ab79f15 diff --git a/test/expected/REDDIT/2018-10-09_15-00_RADV_vs__AMDVLK_vs__Rad.html b/test/expected/REDDIT/2018-10-09_15-00_RADV_vs__AMDVLK_vs__Rad.html new file mode 100644 index 0000000..dd99bce --- /dev/null +++ b/test/expected/REDDIT/2018-10-09_15-00_RADV_vs__AMDVLK_vs__Rad.html @@ -0,0 +1,36 @@ + + + + + + + + +
+

RADV vs. AMDVLK vs. Radeon Software Vulkan Driver Performance - October 2018 Linux Gaming

+
([linux_gaming] 2018-10-09_15-00)
+
+ +
+
+ The fact that there are two drivers is the biggest headscratcher from AMD really since they started really doing a good job. I can't see why they are fragmenting that one specific thing rather than just slowly merging it into RADV. +
+
+
+

FlukyS

+
+

The fact that there are two drivers is the biggest headscratcher from AMD really since they started really doing a good job. I can't see why they are fragmenting that one specific thing rather than just slowly merging it into RADV.

+
+

PolygonKiwii

+
+

Because radv isn't their driver and amdvlk shares its code with the windows driver.

But it's not that bad, as the biggest performance gains will likely come from optimizing llvm, which both drivers make use of*.

Also it's not a problem to install two Vulkan drivers side by side so users could always do that if they really need both.

* except for the pro stack, which uses a proprietary compiler shared with windows. I think their plan was to improve llvm and replace the proprietary compiler when llvm caught up in performance, but don't quote me on that

+
+
+
+