Jump to content

View more

Image of the Day

雑魚は多めにして、爽快感重視にしつつ・・・(´・ω・`)
早いとこ、ベースを作って、完成にもっていかないとね。
タイトルもまだ迷ってるだよなぁ。 
#indiedev  #indiegame #screenshotsaturday https://t.co/IwVbswGrhe
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.


Sign up now

DirectX 11 Noobie Performance Question

4: Adsense

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.


  • You cannot reply to this topic
2 replies to this topic

#1 jdub   Members   

459
Like
0Likes
Like

Posted 28 November 2012 - 04:31 PM

I was wondering if there's a significant performance advantage to batching together the rendering of scene objects which use the same shader?
J.W.

#2 Jason Z   Members   

6430
Like
1Likes
Like

Posted 28 November 2012 - 08:10 PM

There is potentially a performance advantage. In general you can say that fewer draw calls should be better, but that all depends on what else is going on in your rendered scene. There isn't a straight answer for these type of questions really, you have to profile your application and see what works best in a given circumstance.

#3 Nik02   Members   

4297
Like
0Likes
Like

Posted 30 November 2012 - 05:57 AM

Generally speaking, the fewer state changes, the better. Of course, if you use heavy logic to implement the batching itself, at some point it ceases to be worthwhile.

If you have a strong GPU but weak CPU (rough measures, I know), you likely benefit more from batching than with a system with strong CPU but relatively weak GPU. Each state change will consume CPU time, even though the setup time on the GPU hardware would be very fast.

Edited by Nik02, 30 November 2012 - 06:04 AM.

Niko Suni





Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.