This document discusses data-oriented design and how it can improve performance over object-oriented design. It advocates that code should follow data organization rather than forcing data into objects. It shows an example of restructuring code from an array of objects to a structure of arrays format to improve memory access and enable parallelization. The key messages are that optimizing for data access and memory performance is important, not all data needs to be in objects, and data-oriented design can lead to better performing and simpler code.

1. Data-Oriented Design@Neku42max.klyga@gmail.com

3. UnreasonedOOD

5. PROGRAMDATADATA

6. Good code follows good data, not the other way around.

7. class Bot{Vector3 position;…float mod;…float aimDirection;…voidUpdateAim(Vector3 target) { aimDirection = Vector3.DotProduct(position, target) * mod; }}

8. class Bot{Vector3 position;…float mod;…float aimDirection;…voidUpdateAim(Vector3 target) { aimDirection = Vector3.DotProduct(position, target) * mod; }}Icache-miss

9. class Bot{Vector3 position;…float mod;…float aimDirection;…voidUpdateAim(Vector3 target) { aimDirection = Vector3.DotProduct(position, target) * mod; }}Icache-missdata-miss

10. class Bot{Vector3 position;…float mod;…float aimDirection;…voidUpdateAim(Vector3 target) { aimDirection = Vector3.DotProduct(position, target) * mod; }}UNUSEDIcache-missdata-miss

11. ………………

12. Array of StructuresStructure of Arraysclass Bot{Vector3 position;…float mod;…float aimDirection;…}List<Bot> bots;class Bots{List<Vector3> positions;…List<float> mods;…List<float> aimDirections;…}

13. class Bot{… voidUpdateAim(Vector3 target) { aimDirection = Vector3.DotProduct(position, target) * mod; }}class Bots{… staticvoidUpdateAims(List<float> aimDirections,List<Vector3> positions, List<float> mods, List<Vector3> targets) { for (uint i = 0; i < aimDirections.Count; ++i)aimDirections[i] = Vector3.DotProduct(positions[i], targets[i]) * mods[i]; }}

14. Know the data!Think! Think! Think!

15. It’s all about memoryOptimize for data not code

16. It’s all about memoryOptimize for data not codeMost code is mostly bound to memory access

17. It’s all about memoryOptimize for data not codeMost code is mostly bound to memory accessNot everything needs to be an object

18. Data-Oriented Design:Better performance

19. Data-Oriented Design:Better performanceOften simpler code

20. Data-Oriented Design:Better performanceOften simpler codeMore parallelizable code

21. Questions?

22. http://slidesha.re/hKF9er