Uniqcli

Edge location latency budget

Separate round-trip propagation floor from entered queueing and application processing allowances.

Networking

Edge location latency budget

Separate round-trip propagation floor from entered queueing and application processing allowances.

Example inputs · Replace these with your measurements to build your plan.

Method, example and sources
  1. Use the actual one-way path length rather than map distance.
  2. Multiply distance by two and divide by entered propagation speed.
  3. Add the separate queue/transit and application allowances.
  4. Compare the resulting budget with the response-time target.

Worked example. A 1,000 km path at 200,000 km/s has a 10 ms propagation RTT floor. Adding 6 ms transit and 12 ms processing gives 28 ms.

Planning result · confirm model details

Inside this latency budget

Round-trip propagation uses the entered one-way path length, not straight-line map distance.

Propagation RTT floor
10ms
Modeled response latency
28ms
Target margin
22ms
  • 200,000 km/s is an editable approximate fiber propagation speed. Routing stretch, access links, serialization and protocol round trips require measurements or separate allowances.

From the catalog

Servers

Explore related listings, then confirm the exact model requirements against your plan. These listings are not an automatic compatibility or capacity verdict.

Browse servers Browse routers & gateways Get help with the specification

How to use this result

Placing compute closer to its users can reduce distance-related delay, but distance is only one part of response time. This worksheet shows propagation separately so server processing and queueing do not disappear into a single number. A fiber path often travels farther than a direct line between the two sites; use an informed routed-path estimate.

What to verify next

The result is an entered budget, not a ping measurement or a site recommendation. Access networks, serialization, retransmissions and protocol handshakes can add delay beyond the propagation floor. Compare measured latency distributions and the complete workload before choosing an edge system. A nearby server with insufficient processing capacity may still respond more slowly than a distant well-provisioned service.

Worked example

A 1,000 km path at 200,000 km/s has a 10 ms propagation RTT floor. Adding 6 ms transit and 12 ms processing gives 28 ms.

Edge location latency budget — Uniqcli