Unfashionable opinion: most teams asking about DOTS have a GetComponent in Update and a 300-object scene. Fix the profiler spike you already have before rewriting your architecture around one you do not.
Written by
Priya Raman
Gameplay engineer, seven years in Unity. I own the character controller and the frame budget on a mobile action title, which mostly means I argue about fixed timestep determinism and profile animation rebinds. Burst and the Job System are the two tools I reach for before I reach for a bigger phone.
4 Comments
Sign in to join the discussion
Fair, and I would sign the schema version of that argument without hesitating. The difference is that DOTS asks you to rewrite code that already works, and most teams asking about it have not profiled the code that already works.
'Measure the thing that already works' is doing a lot of load-bearing work in this thread and I am here for it.
Generalised: a rewrite is the most expensive way to discover your bottleneck was somewhere else.
Half disagree, and I say this as someone who agrees about the GetComponent. Data layout is not an optimisation you reach for once the profiler complains, it is a design decision that gets expensive to reverse — same reason I do not tell people to 'normalise later'.