• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
BenS1

DX11
[DX11] Command Lists on a Single Threaded Renderer

12 posts in this topic

One of the new major features of DirectX 11 is its support for multithreaded rendering using Immediate and Deferred Contexts, however it seems to me that the ability to create a Command List would potentially be beneficial even for a single threaded renderer. Is this correct?

Basically a Command List is a more efficient way of submitting a number of state and draw commands than calling each API separately, so even if you do all your rendering on one thread it would still seem more efficient to use Command Lists to perform repeat lists of actions.

If this is correct, then why isn't this mentioned more? Why are Deferred Contexts pretty much exclusively documented as a multi threading feature?

Thanks
ben
0

Share this post


Link to post
Share on other sites
I'm pretty sure I remembered reading somewhere that the runtime/drivers weren't optimized for this case. However I still think it would be worth trying out, especially as the drivers get better support for deferred command list generation.
0

Share this post


Link to post
Share on other sites
[quote name='MJP' timestamp='1321297420' post='4883879']
I'm pretty sure I remembered reading somewhere that the runtime/drivers weren't optimized for this case. However I still think it would be worth trying out, especially as the drivers get better support for deferred command list generation.
[/quote]
You are right, I just ran a test on 10,000 cubes, single threaded:
[list][*]Immediate: 200 fps[*]Deferred: 150 fps[/list]So Deferred for single threaded application is slower (at least on my machine). Note that checking the threading support for command list for my graphics card (AMD 6970M) is returning false, so I assume that It is not supported natively by the driver but "emulated" by DX11...
0

Share this post


Link to post
Share on other sites
I'm not sure if the AMD GPU's support it yet, but my GTX 470 on latest drivers says that it does. I'll have to check on my HD 6970 when I get home.

If your test is easily packagable, I would be happy to try it out on my machine to see how it performs.
0

Share this post


Link to post
Share on other sites
[quote name='xoofx' timestamp='1321370413' post='4884183']
[quote name='MJP' timestamp='1321297420' post='4883879']
I'm pretty sure I remembered reading somewhere that the runtime/drivers weren't optimized for this case. However I still think it would be worth trying out, especially as the drivers get better support for deferred command list generation.
[/quote]
You are right, I just ran a test on 100,000 cubes, single threaded:
[list][*]Immediate: 200 fps[*]Deferred: 150 fps[/list]So Deferred for single threaded application is slower (at least on my machine). Note that checking the threading support for command list for my graphics card (AMD 6970M) is returning false, so I assume that It is not supported natively by the driver but "emulated" by DX11...
[/quote]
I would caution against making blanket statements about the performance of single vs. deferred rendering - it totally depends on what your renderer does when it is submitting work to the API. For example, if your engine does lots of work in between the API calls that it makes, then it would likely be beneficial to utilize multiple threads which could reduce the total time needed to process a rendering path. On the other hand, if your submission routines are very bare bones and only submits API calls, there could be some benefit to compiling a long list of commands into a command list and then reusing it from frame to frame. This will depend on the hardware, the driver, your engine, and the application that is using your engine - you need to profile and see if it is worth it in a given context. You could even dynamically test it out on the first startup of your application and then choose the appropriate rendering method.

To that end - I would suggest setting up your rendering code to not know if it is using a deferred or immediate context so that you can delay the decision as long as possible as to which method you will use. That is just my own suggestion though - I have found it to be useful, but your mileage may vary!
1

Share this post


Link to post
Share on other sites
[quote name='xoofx' timestamp='1321370413' post='4884183']
[quote name='MJP' timestamp='1321297420' post='4883879']
I'm pretty sure I remembered reading somewhere that the runtime/drivers weren't optimized for this case. However I still think it would be worth trying out, especially as the drivers get better support for deferred command list generation.
[/quote]
You are right, I just ran a test on 100,000 cubes, single threaded:
[list][*]Immediate: 200 fps[*]Deferred: 150 fps[/list]So Deferred for single threaded application is slower (at least on my machine). Note that checking the threading support for command list for my graphics card (AMD 6970M) is returning false, so I assume that It is not supported natively by the driver but "emulated" by DX11...
[/quote]

Thanks all

xoofx, in your test do you re-create the command list every frame, or do you create the command list once at startup and then just re-execute it every frame?

I'm amazed that AMD cards don't support multithreading at the driver level yet!

I'd be interested in seeing the results on a NVidia card too.

Thanks
Ben
0

Share this post


Link to post
Share on other sites
If have released the executable test along some analysis about the results [url="http://code4k.blogspot.com/2011/11/direct3d11-multithreading-micro.html"]here[/url].

Of course, I agree with Jason.Z statements about taking carefully this kind of results, and the fact that a renderer can easily be built to switch transparently from a deferred context to an immediate context.

To respond to your initial question BenS1, It seems that hardware support for command list doesn't seems to change a lot (using a pre-prepared command list once and run it on an immediate context) compare to using the default Direct3D11 behavior.
0

Share this post


Link to post
Share on other sites
The problem with using a deferred context in a single threaded system is that you are doing more work per core in that situation; you have to prepare the CL, which takes some extra CPU overhead as the driver needs to do things and then you have to reaccess it again to send it to the card properly. Spread across multiple threads the cost-per-setup drops significantly and, if you batch them, your send arch will benifit greatly from code cache reuse (and depending on how it's stored maybe some data cache too).

Any speed gain also depends very much on what you are doing; in a test case at work which was setup to be heavily CPU bound, switching on mutli-threading CL support when NV's drivers were updated to fix it did give us a speed boost however it wasn't that much. I then spent some time playing with the test case and discovered that when we got over a certain threshold for data per CL we started spending more and more time in the buffer swapping function than anywhere else in the submission due to the driver having to do more. (I can't recall the specifics but from what I do recall drivers are limited memory wise or something like that... basically we blew a buffer right out).

However up until that point the MT CL rendering WAS making a significant difference with our CPU time usage and we had near perfect scaling [b]for the test case[/b].

The key point from all this; MT CL, if implimented by the drivers, will help but ONLY your CPU time.

I make a point of saying this because there is no 'hardware support' for CL; Command Lists are purely a CPU side thing, the difference is between letting the DX11 runtime cache the commands or letting the driver cache them and optimise them. (AMD still lacks support for this, although it is apprently 'coming soon')

(Also, as a side note, I do recall reading that 'create, store and reuse' isn't an optimal pattern for command lists. The runtime isn't really setup for this case and it assumes you'll be remaking them each frame, which is a fair assumption because as you can't chain them together to adjust each others state and most command lists will change each frame in a 'real world' situation it is best to test against this)
0

Share this post


Link to post
Share on other sites
[quote name='phantom' timestamp='1321785963' post='4885837']
I then spent some time playing with the test case and discovered that when we got over a certain threshold for data per CL we started spending more and more time in the buffer swapping function than anywhere else in the submission due to the driver having to do more. (I can't recall the specifics but from what I do recall drivers are limited memory wise or something like that... basically we blew a buffer right out).[/quote]
this could come from the Map/UnMap on command buffers, with an immediate context that is giving directly a kind of DMA to the GPU memory, but with a deferred context, it has to copy to a temporary buffer (which is probably on the RAM, but not sure it is on a shared memory on the GPU)...

[quote name='phantom' timestamp='1321785963' post='4885837']
I make a point of saying this because there is no 'hardware support' for CL; Command Lists are purely a CPU side thing, the difference is between letting the DX11 runtime cache the commands or letting the driver cache them and optimise them. (AMD still lacks support for this, although it is apprently 'coming soon')
[/quote]
Indeed, if it is natively supported by the driver, It can be optimized. A coworker found also on NVIDIA a performance boost when they introduced support for command list, though on AMD, It is already fine without the support from the driver... probably the command buffer on AMD is already layout in the same way DirectX11 command buffer is layout...
0

Share this post


Link to post
Share on other sites
[quote name='xoofx' timestamp='1321774033' post='4885817']
If have released the executable test along some analysis about the results [url="http://code4k.blogspot.com/2011/11/direct3d11-multithreading-micro.html"]here[/url].

Of course, I agree with Jason.Z statements about taking carefully this kind of results, and the fact that a renderer can easily be built to switch transparently from a deferred context to an immediate context.

To respond to your initial question BenS1, It seems that hardware support for command list doesn't seems to change a lot (using a pre-prepared command list once and run it on an immediate context) compare to using the default Direct3D11 behavior.
[/quote]

Wow, great article! Thanks.

Its a shame that the results show that command lists aren't really a faster way of repeating the same drawing commands over and over for a single threaded renderer.

I suspect they have the potential to be faster if the driver developers had sufficient motivation to optimise this area of their code, especially if they optimised the command list when you call FinishCommandList. I guess the problem is that the driver has no idea if you're only going to use the command list once and throw it away (In which case the act of optimising the command list may cost more than the potential gains), if if you're going to create the comand list once and execute it many times (In which case optimisng the list may be beneficial).

I guess we'd need a tweak to the API so that you can either pass in a boolean to FinishCommandList to tell the driver whether the command list should be optimised or not, or maybe there could be a separate explicit OptimizeCommandList method.

Thanks again for your detailed analysis.

Thanks
Ben
0

Share this post


Link to post
Share on other sites
[quote name='phantom' timestamp='1321785963' post='4885837']
The problem with using a deferred context in a single threaded system is that you are doing more work per core in that situation; you have to prepare the CL, which takes some extra CPU overhead as the driver needs to do things and then you have to reaccess it again to send it to the card properly. Spread across multiple threads the cost-per-setup drops significantly and, if you batch them, your send arch will benifit greatly from code cache reuse (and depending on how it's stored maybe some data cache too).

<snip>

(Also, as a side note, I do recall reading that 'create, store and reuse' isn't an optimal pattern for command lists. The runtime isn't really setup for this case and it assumes you'll be remaking them each frame, which is a fair assumption because as you can't chain them together to adjust each others state and most command lists will change each frame in a 'real world' situation it is best to test against this)
[/quote]

Thanks Phantom, but in my case I was thinking of creating the command list once and then executing it for each frame.

As I'm sure you know, a command list containing a constant buffer will only contain references (Or pointers) to the constant buffer and not the actual data containined int he buffer itself, so an app can still change the data in the constant buffer from frame to frame without having to create a new command list.

So for example I was thinking:
1. At startup create a command list (DrawTankCL) that draws a Tank at a position defined in a Contant Buffer ("TankCB")
2. Update TankCB.position on the CPU based on user input, physics etc
3. ExecuteCommandList(DrawTankCL)
4. Repeat from step 2.

As you can see the command list is created once and executed over and over, and yet the tanks posiiton is still dynamic.

Its a shame that this "create, store, reuse" pattern is not optimised int he drivers.

Anyway, at least now I know the answer so I code my game accordingly.

Thanks for your help
Ben
0

Share this post


Link to post
Share on other sites
There are two problems with your idea.

Firstly, you are being too fine grain with your CL for it to really be useful. There is a good PDF from GDC2011 which covers some of this (google: Jon Jansen DX11 Performance Gems, that should get you it). The main thing is that a CL has overhead, apprently a few dozen API calls so doing too little work in one is going to be a problem as it will just get swamped with overhead. Depending on your setup scenes or material groups are better fits for CL building and execution.

Secondly; you run the risk of suffering a stall at step 2. The driver buffers commands and the GPU should be working at the same time as you execute other work, so there is a chance that when you come to update in step 2 you could be waiting a 'significant' amount of time for the GPU to be done with your buffer and release it so that you can update it again. Discard/lock or other update [i]might[/i] avoid the problem, I've not tried it myself, but it still presents an issue.
0

Share this post


Link to post
Share on other sites
[quote name='xoofx' timestamp='1321790455' post='4885852']
Indeed, if it is natively supported by the driver, It can be optimized. A coworker found also on NVIDIA a performance boost when they introduced support for command list, though on AMD, It is already fine without the support from the driver... probably the command buffer on AMD is already layout in the same way DirectX11 command buffer is layout...
[/quote]

NV is a strange beast; before they had 'proper' support they kinda emulated it by spinning up a 'server' thread and serialising the CL creation via that. Amusingly if any of your active threads ended up on the same core as the server thread it tended to murder performance but by staying clear you could get a small improvement. Once the drivers came out which did the work correctly this problem went away.

In our test NV with proper support soundly beat AMD without it; this was a 470GTX vs 5870 on otherwise basically identical hardware (i7 CPUs, the NV one had a few hundred Mhz over the AMD one, but not enough for the performance delta seen). AMD's performance was more in line with the single thread version. However our test was a very heavy CPU bound one; 15,000 draw calls spread over 6 cores each one drawing a single flat shaded cube. Basically an API worse nightmare ;)

(Amusing side note; the same test/code on an X360 @ 720p could render at a solid 60fps with a solid 16.6ms frame time. That's command lists being generated each frame over 6 cores; shows just how much CPU overhead/performance loss you take when running on Windows :( )
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Similar Content

    • By AireSpringfield
      Hi,
        I started reading Introduction to 3D Game Programming with Direct3D 11.0 and have a little question about callback function. In author's example code d3dApp.cpp, he managed to assign a member function to WNDCLASS::lpfnWndProc
      namespace {     // This is just used to forward Windows messages from a global window     // procedure to our member function window procedure because we cannot     // assign a member function to WNDCLASS::lpfnWndProc.     D3DApp* gd3dApp = 0; } LRESULT CALLBACK MainWndProc(HWND hwnd, UINT msg, WPARAM wParam, LPARAM lParam) {     // Forward hwnd on because we can get messages (e.g., WM_CREATE)     // before CreateWindow returns, and thus before mhMainWnd is valid.     return gd3dApp->MsgProc(hwnd, msg, wParam, lParam); } in constructor D3DApp::D3DApp()
      gd3dApp = this; and in bool D3DApp::InitMainWindow()
      wc.lpfnWndProc = MainWndProc; Notice that D3DApp::MsgProc is a virtual function. 
      As far as I'm concerned, I would find it convenient to declare MsgProc member function as static. However, a static member can't be virtual. Is there any solution so that I can overcome the contradiction except author's method?
       
    • By Holy Fuzz
      I am working on a game (shameless plug: Cosmoteer) that is written in a custom game engine on top of Direct3D 11. (It's written in C# using SharpDX, though I think that's immaterial to the problem at hand.)
      The problem I'm having is that a small but understandably-frustrated percentage of my players (about 1.5% of about 10K players/day) are getting frequent device hangs. Specifically, the call to IDXGISwapChain::Present() is failing with DXGI_ERROR_DEVICE_REMOVED, and calling GetDeviceRemovedReason() returns DXGI_ERROR_DEVICE_HUNG. I'm not ready to dismiss the errors as unsolveable driver issues because these players claim to not be having problems with any other games, and there are more complaints on my own forums about this issue than there are for games with orders of magnitude more players.
      My first debugging step was, of course, to turn on the Direct3D debug layer and look for any errors/warnings in the output. Locally, the game runs 100% free of any errors or warnings. (And yes, I verified that I'm actually getting debug output by deliberately causing a warning.) I've also had several players run the game with the debug layer turned on, and they are also 100% free of errors/warnings, except for the actual hung device:
      [MessageIdDeviceRemovalProcessAtFault] [Error] [Execution] : ID3D11Device::RemoveDevice: Device removal has been triggered for the following reason (DXGI_ERROR_DEVICE_HUNG: The Device took an unreasonable amount of time to execute its commands, or the hardware crashed/hung. As a result, the TDR (Timeout Detection and Recovery) mechanism has been triggered. The current Device Context was executing commands when the hang occurred. The application may want to respawn and fallback to less aggressive use of the display hardware). So something my game is doing is causing the device to hang and the TDR to be triggered for a small percentage of players. The latest update of my game measures the time spent in IDXGISwapChain::Present(), and indeed in every case of a hung device, it spends more than 2 seconds in Present() before returning the error. AFAIK my game isn't doing anything particularly "aggressive" with the display hardware, and logs report that average FPS for the few seconds before the hang is usually 60+.
      So now I'm pretty stumped! I have zero clues about what specifically could be causing the hung device for these players, and I can only debug post-mortem since I can't reproduce the issue locally. Are there any additional ways to figure out what could be causing a hung device? Are there any common causes of this?
      Here's my remarkably un-interesting Present() call:
      SwapChain.Present(_vsyncIn ? 1 : 0, PresentFlags.None); I'd be happy to share any other code that might be relevant, though I don't myself know what that might be. (And if anyone is feeling especially generous with their time and wants to look at my full code, I can give you read access to my Git repo on Bitbucket.)
      Some additional clues and things I've already investigated:
      1. The errors happen on all OS'es my game supports (Windows 7, 8, 10, both 32-bit and 64-bit), GPU vendors (Intel, Nvidia, AMD), and driver versions. I've been unable to discern any patterns with the game hanging on specific hardware or drivers.
      2. For the most part, the hang seems to happen at random. Some individual players report it crashes in somewhat consistent places (such as on startup or when doing a certain action in the game), but there is no consistency between players.
      3. Many players have reported that turning on V-Sync significantly reduces (but does not eliminate) the errors.
      4. I have assured that my code never makes calls to the immediate context or DXGI on multiple threads at the same time by wrapping literally every call to the immediate context and DXGI in a mutex region (C# lock statement). (My code *does* sometimes make calls to the immediate context off the main thread to create resources, but these calls are always synchronized with the main thread.) I also tried synchronizing all calls to the D3D device as well, even though that's supposed to be thread-safe. (Which did not solve *this* problem, but did, curiously, fix another crash a few players were having.)
      5. The handful of places where my game accesses memory through pointers (it's written in C#, so it's pretty rare to use raw pointers) are done through a special SafePtr that guards against out-of-bounds access and checks to make sure the memory hasn't been deallocated/unmapped. So I'm 99% sure I'm not writing to memory I shouldn't be writing to.
      6. None of my shaders use any loops.
      Thanks for any clues or insights you can provide. I know there's not a lot to go on here, which is part of my problem. I'm coming to you all because I'm out of ideas for what do investigate next, and I'm hoping someone else here has ideas for possible causes I can investigate.
      Thanks again!
       
    • By thmfrnk
      Hello,
      I am working on a Deferred Shading Engine, which actually uses MSAA for Antialising. Apart from the big G-Buffer ressources its working fine. But the intention of my engine is not only realtime-rendering as also render Screenshots as well as Videos. In that case I've enough time to do everything to get the best results. While using 8x MSAA, some scenes might still flicker.. especially on vegetations. Unfortunately 8x seems to be the maximum on DX11 Hardware, so there is no way to get better results, even if don't prefer realtime.
      So finally I am looking for a solution, which might offer an unlimited Sample count. The first thing I thought about was to find a way to manually manipulate MSAA Sample locations, in order to be able to render multiple frames with different patterns and combining them. I found out that NVIDIA did something equal with TXAA. However, I only found a solution to use NVAPI, in order to change sample locations. https://mynameismjp.wordpress.com/2015/09/13/programmable-sample-points/
      While I am working on .NET and SlimDX I've no idea how hard it would to implement the NVIDIA API and if its possible to use it together with SlimDX. And this approach would be also limited to NV.
      Does anyone have an idea or maybe a better approach I could use?
      Thanks, Thomas
    • By matt77hias
      For vector operations which mathematically result in a single scalar f (such as XMVector3Length or XMPlaneDotCoord), which of the following extractions from an XMVECTOR is preferred:
      1. The very explicit store operation
      const XMVECTOR v = ...; float f; XMStoreFloat(&f, v); 2. A shorter but less explicit version (note that const can now be used explicitly)
      const XMVECTOR v = ...; const float f = XMVectorGetX(v);  
    • By Coelancanth
      Hi guys,
      this is a exam question regarding alpha blending, however there is no official solution, so i am wondering  whether my solution is right or not... thanks in advance...

      my idea:
      BS1:
      since BS1 with BlendEnable set as false, just write value into back buffer.
      -A : (0.4, 0.4, 0.0, 0.5)
      -B : (0.2, 0.4, 0.8, 0.5)
       
      BS2:
       
      backbuffer.RGB: = (0.4, 0.0, 0.0) * 1 + (0.0, 0.0, 0.0) * (1-0.5)      = ( 0.4, 0.0, 0.0)
      backbuffer.Alpha = 1*1 + 0*0   =1
       
      A.RGB = (0.4, 0.4, 0.0)* 0.5 + (0.4, 0.0, 0.0)* ( 1-0.5)   = (0.4,0.2,0.0)
      A.Alpha=0.5*1+1*(1-0.5) = 1
       
       
      B.RGB = (0.2, 0.4, 0.8) * 0.5 + (0.4, 0.2, 0.0) * (1-0.5)  = (0.3, 0.3, 0.4)
      B.Alpha = 0.5 * 1 + 1*(1-0.5)  = 1
       
      ==========================
      BS3:
       
      backbuffer.RGB = (0.4, 0.0, 0.0) + (0.0, 0.0, 0.0)  = (0.4, 0.0, 0.0)
      backbuffer.Alpha = 0
       
      A.RGB = (0.4, 0.4, 0.0) + (0.4, 0.0, 0.0) = (0.8, 0.4, 0.0)
      A.Alpha = 0
       
      B.RGB = (0.2, 0.4, 0.8) + (0.8, 0.4, 0.0) = (1.0, 0.8, 0.8)
      B.Alpha = 0
       
       
       
  • Popular Now