Basemark GPU DX12 VS Vulkan Performance Review

4K Testing

Basemark GPU DX12 VS Vulkan Performance Review

4K Testing

By default, Basemark GPU's primary graphical test is run at 4K High settings, maximising GPU load to make the benchmark primarily GPU limited. At this resolution, we will run tests in the benchmark at default (High) settings and see which GPU manufacturer and API offers the highest performance levels when things are as GPU constrained as possible.

4K Results  

In the graph below we can see a similar trend to our 1080p results, though this time AMD's graphics cards put up a better fight against their Geforce counterparts, with the RX Vege 56 surpassing the GTX 1070 and the RX 580 surpass the GTX 1060 when using the DirectX 12 or Vulkan APIs.    

OpenGL remains a weak spot for AMD, even at 4K with Nvidia's GTX series GPUs offering similar performance levels on all APIs at 4K. This is precisely why we decided to test Basemark GPU at lower resolutions, as this better highlights the shortcomings of the OpenGL API. 

To order this chart we took an average of results for all three APIs, which is why AMD's graphics cards sit below their Nvidia counterparts. Sadly our tester has no Nvidia RTX series graphics cards in-house to add to our API testing in Basemark GPU. 


Basemark GPU DX12 VS Vulkan Performance Review  

«Prev 1 2 3 4 Next»

Most Recent Comments

29-11-2018, 15:19:39

Given Vulkan is a direct evolution of Mantle's source code it's intriguing to see DX12 still hold a small advantage on AMDs cards. I guess it could be down to the Xbone's use of both GCN and DX12 putting more optimisation work into the combination than traditionally considered worthwhile(Low level APIs are much more dependant on game/app/API side optimisations than driver side; Most work AMD/NVidia do for DX12/Vulkan games are for the game code itself rather than their drivers).Quote

29-11-2018, 15:30:39

It's also quite closely related to modern OpenGL isn't it? Though I'm not a graphics developer, rather not a developer at all, but my understanding was that modern OGL allowed devs to operate with little abstraction, but the API is a convoluted mess overall.Quote

29-11-2018, 16:11:22

While Vulkan is the successor to OpenGL and is also maintained by Khronos group and has an externally similar syntax regarding the developer-facing API calls (Very C-like), the code-base itself was built entirely from scratch (By AMD) and I believe has no legacy code from OpenGL whatsoever.Quote

29-11-2018, 17:57:49

With some Google-fu it seems that the strongest (api) relation between the two is that there's a library which allows running OpenGL ES on top of vulkan using something called GLOVE. Quote

Register for the OC3D Newsletter

Subscribing to the OC3D newsletter will keep you up-to-date on the latest technology reviews, competitions and goings-on at Overclock3D. We won't share your email address with ANYONE, and we will only email you with updates on site news, reviews, and competitions and you can unsubscribe easily at any time.

Simply enter your name and email address into the box below and be sure to click on the links in the confirmation emails that will arrive in your e-mail shortly after to complete the registration.

If you run into any problems, just drop us a message on the forums.