structural-change-cost-model

To avoid chunk migration spikes in Unity DOTS, select the lowest-cost ECS state transition using a frequency-based decision model. For high-frequency updates exceeding one per second per entity, enforce O(1) operations like value mutation or enableable component toggling instead of structural changes.

The cheapest way to handle frequent ECS state transitions is applying a frequency rule of thumb. If a state changes more than once per second per entity, choose O(1) value mutation or enableable component toggling over structural add/remove operations to minimize archetype churn and runtime frame spikes.

Use structural add/remove operations in ECS for low-frequency, semantically meaningful archetype boundaries, such as marking entities as Dead to exclude them from queries. Use enableable component toggling for high-frequency state changes to prevent chunk migration spikes.

Reduce archetype churn during high-frequency entity state changes by enforcing O(1) transition choices. Apply a canonical decision model that defaults to value mutation or enableable component toggling for updates exceeding one per second, reserving structural changes for rare transitions.

Unity DOTS performance optimization requires avoiding structural changes for high-frequency entity state updates. A canonical decision model enforces O(1) transitions like value mutation and enableable toggling to minimize archetype churn and chunk migration, maintaining predictable runtime frame rates.