Introduction to Data-Oriented Design in Unity
summary
Introduces Unity DOTS with concrete examples: uses moving 1,000 entities to show float3 positions, per-entity move speed and single-player input, stores components in structure of arrays inside 16KB chunks, and runs systems via Entities.ForEach or IJobEntity scheduled with the C# Job System. Demonstrates IEComponentData, baker authoring, and Burst-compiled SIMD output (vaddps/vmovaps) for big CPU gains. Notes JetBrains Rider DOTS templates, editor quirks, separate physics/UX bridges, and a smaller hiring pool as tradeoffs.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:24Data-Oriented Design
- 7:45Unity’s DOTS
- 9:11ECS core concepts
- 12:40C# Job System
- 14:45Burst compiler
- 16:53Moving entities example
- 25:17DOTS development notes
- 27:25Why use DOTS
- 29:30DOTS challenges
- 31:39DOTS learning
- 34:05Q&A
related talks
08mCodemotion Berlin 2019 I Ciro Continisio, Lead Evangelist, EMEA - Unity Technologies (Interview)
59mWhy DOTS Is Unity's Silver Bullet
56mDOTS authoring and debugging workflows in the Unity Editor
59mThe path to leveraging DOTS in production
39mA revolution is coming! Writing performant and safe multi threaded code in Unity
10mThe future of Unity (Entity Component System & Performance)
01h 05mData Storage in Entity Component Systems
41mBeyond OOP: A Journey From Cache Misses to MASS Hits