Controller-Path Latency Budget
Controller-Path Latency Budget
Before treating controller placement as an availability answer, use the latency budget below to separate the path terms that placement actually removes from queue and compute terms that remain. The preset begins with a local gateway loop and a cloud loop; increase only local queueing to test the counterexample in which the apparently nearer controller path becomes slower.
Use the resulting dominant term and budget margin as evidence in the failover record. A shorter physical path is useful only when ownership transfer, queueing, processing, and return traffic still fit the service deadline.