Data-Oriented Design and C++
summary
The claim is stark: transformation of data is the only purpose and common C++ idioms in console games actively impede that goal. Concrete examples show tight, performance-critical systems — rendering, animation, streaming, VFX — and dozens of in-house tools that must process huge streams of objects at frame rate. The talk demonstrates specific code patterns, measurable slowdowns, and compiler limitations that force design tradeoffs, plus what changed when data-oriented layouts and algorithms replace object-centric ones.
AI-written summary · about
chapters (5)
- 0:00Start
- 28:55A little review...
- 31:11L2 cache misses/frame
- 41:48Some common issues...
- 54:10Let's review some code...
related talks
53mCan C++ Data-oriented-design be Improved?
01h 30mC++ in Constrained Environments
01h 03mWriting sustainable software. The how and the what!
50mThinking Functionally in C++
51mC++ Game Development - Many Ways to Kill an Orc (or a Hero)
43mClosing Keynote
39mYou Got Your Idris in My C++! A First Look at Denotational Design
01h 04mAbstraction Patterns for Cross Platform Development Using C++