Data-oriented design: Difference between revisions

Revision as of 23:32, 7 December 2020

Revision as of 08:25, 8 December 2020

Line 1:

{{Distinguish|Data-driven programming}}

{{More citations needed|date=July 2020}}

In [[computing]], '''data-oriented design''' is a [[program optimization]] approach motivated by efficient usage of the [[CPU cache]], used in [[video game]] development.<ref>{{cite web|url=http://gamesfromwithin.com/data-oriented-design|title=Data-oriented design|last=Llopis|first=Noel|date=December 4, 2009|website=Data-Oriented Design (Or Why You Might Be Shooting Yourself in The Foot With OOP)|url-status=live|archive-url=|archive-date=|access-date=April 17, 2020}}</ref>. The approach is to focus on the data layout, separating and sorting [[field (computing)|fields]] according to when they are needed, and to think about transformations of data. Proponents include Mike Acton<ref>{{cite web|title=CppCon 2014: Mike Acton "Data-Oriented Design and C++"|url=https://www.youtube.com/watch?v=rX0ItVEVjHc}}</ref> and [[Scott Meyers]].<ref>{{cite web|title=code::dive conference 2014 - Scott Meyers: Cpu Caches and Why You Care|url=https://www.youtube.com/watch?v=WDIkqP4JbkE}}</ref>

== Motives ==