Start Updating parameters chicken processing line model

Updating parameters chicken processing line model

You can create multiple command lists, and create a thread for each list, to add the commands to it, so that they can all work in parallel.

This way the programmer can shave off redundant work and reduce overhead on the CPU side.

The API calls are now lighter and simpler, because they don’t have to take care of all the bookkeeping, validation and other types of management.

but vendor A’s hardware is designed more for DX12/Vulkan than vendor B’s”.

It’s a bit more complicated than that, because it is somewhat of a chicken-and-egg problem.

There were however two problems with this approach: To clarify that second point, Future Mark built an API overhead test, which includes tests with DX11 using immediate and deferred contexts, with a single or multiple threads. As you can see, this feature does absolutely nothing on AMD hardware.

They are stuck at 1.1M calls regardless of what technique you use, or how many cores you throw at it.

A big problem in this programming model is that the order in which the commands are executed, is important.

That basically means that you can only use a single thread to send commands.

So I thought I’d do a quick blog to try and explain it.

A large part of the confusion seems to be because the capabilities of hardware tend to be categorized by versions of the Direct X API.

But, as you can also see, these have been ‘backported’ to Direct X 11.3 as well, so apparently they are not specific to the Direct X 12 API. And the ‘new thing’ about Direct X 12, Vulkan (and Metal and Mantle) is that the interface follows a new paradigm, a new programming model.