Jump to content
  • Advertisement
Sign in to follow this  
jakovo

DX11 Performance improvements from Dx9 to Dx10/11

This topic is 2052 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi,

 

I was in an interview last week, and one of the questions I was asked was "What peformance improvements were made into DirectX when moving from Dx9 to Dx10/11?"...

 

I have worked with Dx9 and Dx11, but this question totally freaked me out, because I don't know (maybe I'm still very young on this); however, I remember to have read that it reduced "micro-batching" (although I don't know how it does so or why).

 

So, I thought that it would be a good idea to ask you guys and learn a little bit about it....  so, basically that's the question, what improvements were made in the API / Architecture when changing from Dx9 to Dx10/11 that helped to improve the performance?

 

Thanks!

Share this post


Link to post
Share on other sites
Advertisement

Thanks MJP!

 

uhmmm... yeah, makes sense what you say!... very interesting...

 

like what old cruft do you refer to?...

 

by saying: "having access to more functionality" you refer to all the spec's provided on the upper feature levels, right? 

 

 

Thanks again!

Share this post


Link to post
Share on other sites

"Old cruft" would mostly refer to the fixed-function pipeline and everything that went with it.

 

As for "more functionality", yes this would mostly be the things enabled by the higher feature levels. So things like new shader types, new resource types (texture arrays, structured buffers, append buffers), access to MSAA sample data, new texture sampling functions (Gather, SampleCmp), integer instructions, new render target and compressed texture formats, etc.

Share this post


Link to post
Share on other sites

MJP's hit the nail on the head already wink.png

Another "more functionality" thing is that compute shaders offer new ways of structuring your computation. Many image processing algorithms, like summed area tables are much easier to implement in a compute shader than a fragment shader. With unordered-access-views, shaders can now perform arbitrary reads and writes to memory, which allows many more types of algorithms to be implemented on the GPU.

Share this post


Link to post
Share on other sites

cool!... 

 

I think that has clarified my mind now...

 

thank you both!... =)

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!