The core of DOTS is really just cache-line economics wearing a fancy architectural costume. The historical shift from OOP ECS to Data-Oriented Design came down to the fact that a pure Array-of-Structures layout forces the CPU to load entire cache lines (64 bytes) when you only need a couple of floats per entity—so iterating 10,000 entities with a Position (vec3) and Velocity (vec3) struct wastes ~75% of each memory read on padding and dead fields. Unity’s fix with SoA (Structure-of-Arrays) is that you lay out all X positions contiguously, all Y, all Z, which lets the compiler auto-vectorize into AVX/FMA instructions and lets the prefetcher actually predict access patterns. The pragmatic middle ground most production teams land on is AOSOA—sub-arrays of 4 or 8 interleaved structs—which preserves some natural grouping while still hitting SIMD width boundaries cleanly. If you’re pushing millions of entities on consumer hardware, don’t trust the compiler blindly; profile with VTune or dotTrace Performance Profiler and watch the L2/L3 hit rate, because that’s the real tell that your Archetype layout is working.
For next-gen projections, I’d keep an eye on how Unity is pushing toward more aggressive archetype compaction and the Data Dependency System (DDS) to replace manual job scheduling with compiler-inferred parallelism—the real win is eliminating hand-written [ChunkUpdate] ordering bugs. On the hardware side,
"____________________________________"
"Positioning beats raw aim 9 times out of 10."
