Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Some games use multithreaded renderers as a core design philosophy.</p> <p>For instance... thread 1 calculates all of the game logic, then sends this information to thread 2. Thread 2 precalculates a display list and passes this to the GPU. Thread 1 ends up running 2 frames behind the GPU, thread 2 runs one frame behind the GPU.</p> <p>The advantage is really that you can in theory do twice as much work in a frame. Skinning can be done on the CPU and can become "free" in terms of CPU and GPU time. It does require double buffering a large amount of data and careful construction of your engine flow so that all threads stall when (and only when) necessary.</p> <p>Aside from this, a pretty common technique these days is to have a number of "worker threads" running. Tasks with a common interface can be added to a shared (threadsafe) queue and executed by the worker threads. The main game thread then adds these tasks to the queue before the results are needed and continues with other processing. When the results are eventually required, the main thread has the ability to stall until the worker threads have finished processing all of the required tasks.</p> <p>For instance, an expensive for loop can be changed to used tasks.</p> <pre><code>// Single threaded method. for (i = 0; i &lt; numExpensiveThings; i++) { ProcessExpensiveThings (expensiveThings[i]); } // Accomplishes the same work, using N worker threads. for (i = 0; i &lt; numExpensiveThings; i++) { AddTask (ProcessExpensiveThingsTask, i); } WaitForAll (ProcessExpensiveThingsTask); </code></pre> <p>You can do this whenever you're guaranteed that ProcessExpensiveThings() is thread-safe with respect to other calls. If you have 80 things at 1ms each and 8 worker threads, you've saved yourself roughly 70ms. (Well, not really, but it's a good hand-wavy approximation.)</p>
    singulars
    1. This table or related slice is empty.
    1. POMultithreading in XNA game
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDan Olson
    1. USDan Olson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COGood description :) In addition (since this question was about XNA), it should be noted that the Xbox 360 only has 6 threads, 2 of which are reserved and 4 are available to you. You should only expect to be able to get improvements from having up to 4 threads. (In addition, the 6 threads are actually running on only 3 cores so it's not going to be perfectly comparable improvement)
      singulars
      1. PO
      1. USSean Colombo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload