Data-oriented design: Difference between revisions

Revision as of 04:18, 12 June 2016

Revision as of 04:19, 12 June 2016

Line 1:

In [[computing]], '''Data oriented design''' is an optimisation approach motivated by [[cache coherency]], used in game development. The approach is to focus on the [[data layout]], separating and sorting [[field (computing)|fields]]s according to when they are needed, and to think about transformations of data, rather than following an [[object-oriented]] design methodology. In this approach code follows data, rather than the other way round. The techniques became especially popular during the [[PS3]] and [[xbox 360]] console generation when the hazards of [[cache misses]] became pronounced due to their use of [[in order processors]] and high clock speeds.

Proponents include [[Mike acton]].

Line 6:

{{stub}}

=== See also ===

* [[CPU cache]]

* [[AOS vs SOA]]

* [[memory access pattern]]

[[category:computing]]