Orchestrator
CostComponent
The three things a container can be expensive in.
generated from the sources
Enum in namespace
Nebula · Packages/com.1by3.nebula/Runtime/Orchestrator/ContainerCost.cspublic enum CostComponentThe three things a container can be expensive in. Interest management limits the second and the third but not the first, so "this container is hot" is not one number: a boss arena full of NPCs and a plaza full of players want opposite fixes, and the operator has to be able to tell them apart (docs/cost-telemetry.md).
Members
| Name | Value | Description |
|---|---|---|
Simulation | Simulating the container's own entities: the NetworkTick callbacks the worker ran for them. | |
Replication | Replicating them: world state, netvars and sync state leaving the worker for gateways. | |
Gateway | The per-client relay: owner state, which a gateway forwards to exactly one client each. |
CostBalancedAssignmentPolicy
Deal by load: every container (baked or runtime) costs what CostWeights says its occupants cost, containers are ordered along a Morton curve of their centres so neighbours sit next to each other, and the curve is cut into one contiguous ...
CostWeights
How much simulating a container costs a worker, from what is inside it.