#Difference between directx 11 and 12 driver#
#Difference between directx 11 and 12 windows 10#

And this still comes without some of the potential fringe benefits of the API, such as shifting the TDP balance from CPU to GPU in TDP-constrained mobile devices. So although DirectX 12 is not going to bring the same kind of massive performance improvements to iGPUs that we’ve seen with dGPUs, in extreme cases such as this it still can be highly beneficial.

This simple API switch is still enough to get another 44% out of the A10-7800 and 25% out of the A8-7600. Aside from the GTX 770 – which has the most GPU headroom to spare in the first place – both AMD APUs still see significant performance gains from DirectX 12 despite running into a very quick GPU bottleneck. The fact that AMD no longer lags Intel in batch submission times at this point is very important for AMD, as it means they’re not struggling with individual thread performance nearly as much under DirectX 12 as they were DirectX 11.įinally, taking a look at how performance scales with our GPUs, the results are unsurprising but none the less positive for AMD. Meanwhile batch submission times are consistent between all 3 CPUs, with everyone dropping down from 30ms+ to around 6ms. With this relatively low batch count the benefits of DirectX 12 are still present but diminished, leading to the CPU no longer choking on batch submission and the bottleneck shifting elsewhere (likely the simulation itself). With Extreme quality pushing average batch counts of 90K and Mid pushing 55K, average batch counts under Low are only 20K. Though initially unexpected, examining the batch count differences between Low and Mid qualities gives us a solid explanation as to what’s going on: low pushes relatively few batches. The one exception to this is Low quality mode, where the Core i3 retains its lead. Consequently at Extreme quality we see a 64% performance increase for the Core i3, but a 170%+ performance increase for the AMD APUs. DirectX 12 provides just the kick that the AMD APU setups need to overcome DirectX 11’s CPU submission bottleneck and push it on to the GPU. Highlighting just how bad the single-threaded performance disparity between Intel and AMD can be under DirectX 11, what is a clear 50%+ lead for the Core i3 with Extreme and Mid qualities becomes a dead heat as all 3 CPUs are able to keep the GPU fully fed. To get right down to business then, are AMD’s APUs able to shift the performance bottleneck on to the GPU under DirectX 12? The short answer is yes.

#Difference between directx 11 and 12 windows 10#

Windows 10 Technical Preview 2 (Build 9926)

#Difference between directx 11 and 12 driver#

And as a reminder, this is an early driver on an early OS running an early DirectX 12 application, so everything here is subject to change. Last week we saw how quickly the GPU becomes the bottleneck under Star Swarm when using the DirectX 12 rendering path, and how difficult it is to shift that back to the CPU. To keep things simple, this time we’re running everything on either the iGPU or a GeForce GTX 770. As our initial article was run on various Intel CPU configurations, this time we’re going to take a look at how performance scales on AMD’s Kaveri APUs, including whether DX12 is much help for the iGPU, and if it can help equalize the single-threaded performance gap been Kaveri and Intel’s Core i3 family. It should possibly benefit the Xbox One as well since it uses an API which is similar to DirectX.After several requests and a week’s break from our initial DirectX 12 article, we’re back again with an investigation into Star Swarm DirectX 12 performance scaling on AMD APUs. Other advantages of DX12 include 50% reduction in CPU cycles and bottlenecks in a dual GPU configuration.

Now we are not sure whether this will hold true in case of practical implementation as AMD’s Mantle is still being adopted by developers and DX 12 is still a year away. Surprisingly the performance of draw calls on both the API is similar but when one compares it to DX 11, it’s almost 7.5 times greater.ĭraw Call is one of the performance parameter which is an indication of how many objects can be drawn on the screen and it seems like DX12 and Mantle have the same capacity. Using 3D Mark, Oliver showcased the difference between DirectX 12 and Mantle. During the event, Futuremark’s Oliver Baltuch took center stage to gauge the differences between DirectX 12, DirectX 11 and Mantle.įuturemark’s provides PC and mobile benchmark tools which includes 3DMark. The event was titled Future of Compute and it was attended by the industry’s top developers. AMD recently held a presentation in Singapore talking about the future of GPU technologies.