Edge Computing Latency Comparison Tool
Edge Computing Latency Comparison Tool
Compare edge, fog, cloud, and hybrid response paths with a measured latency budget.
Compare where an IoT response should run before the deadline is missed.
Choose a workload, adjust the modeled path, and watch the event travel through edge, fog, cloud, or hybrid processing. The useful question is not whether edge is always faster; it is which tier can meet the response budget with tail-latency margin.
Load Smart camera alarm with 96 KB Payload per event, 12 Mbps Access bandwidth, and an 80 ms Response budget.
Cloud P95 response crosses 80 ms as WAN distance or Network load rises, while edge P95 retains a positive margin by avoiding both WAN legs.
P95 is estimated as average + 1.65 × jitter + queue tail pressure. Cloud distance changes the two WAN propagation legs; load changes queueing and jitter.
This single-event budget omits packet loss, retries, cold starts, correlated queues, throughput, clock error, failover, and measured P99 deadline probability.
Scenario presets
Path controls
Inspect a path
Animation controls
Response path animation
The event starts at the device, travels to the selected owner, then returns as a command or result.
Latency stack comparison
Each bar uses the same workload. Longer colored segments show which part of the path dominates.
Decision diagnosis
Candidates meeting the P95 budget are ranked by a teaching score for margin, P99, deadline, and compute fit; ties use lower P95.
Use edge for the immediate response and send summarized evidence upstream.
The edge path has enough P95 margin and avoids variable WAN delay.
Confirm the local processor can keep this bound during bursts and software updates.
Percentile view
The dots show modeled average, P95, and P99 estimates for each candidate. The dashed line is the response budget.
Architecture comparison
Use this table after playing with the controls to connect the numeric result to the architecture responsibility.
| Placement | Best when | Latency risk | Evidence to collect |
|---|---|---|---|
| Edge | The decision protects the physical process or must keep working during upstream outages. | Local CPU, memory, accelerator, or actuator response can become the bottleneck. | On-device timing under bursts, firmware updates, thermal limits, and degraded radio conditions. |
| Fog | Several nearby devices need site policy, protocol translation, aggregation, or local coordination. | Gateway queueing and LAN contention can raise the slower percentiles. | Gateway load tests, local failover behavior, buffered replay, and site-level observability. |
| Cloud | The workload benefits from fleet history, elastic compute, long-term storage, or central governance. | WAN distance, routing, congestion, service queues, and cold starts dominate tail latency. | End-to-end traces by region, P95/P99 under load, retries, and service dependency timing. |
| Hybrid | The urgent response stays local while summaries, evidence, or model updates move to cloud later. | Split ownership can hide reconciliation, stale models, or missing audit records. | Local action trace, upstream record lag, conflict handling, and update rollback behavior. |
Gateway loop versus cloud loop
Try: step through the camera event. Observe: the gateway visibly excludes both WAN legs. Explain: use the dominant term and budget margin to justify the winner, then test whether local congestion reverses it.
Gateway wins by 242 ms. The cloud loop is dominated by WAN up at 85 ms.
Common sense/access/actuation floor: 30.0 ms.
Learning support
A latency comparison is useful only when it starts from a workload and a response budget. Measure from the physical event to the useful response, not just from API request to API response.
- Average latency is the arithmetic mean of run latencies, but can hide slow failures.
- P95 latency means 95 out of 100 runs are at or below that value.
- P99 latency is often the better safety or control check because rare slow paths matter.
- Jitter is variation. A path with the same average but higher jitter is harder to trust.
Technical checks
This teaching model uses a transparent budget, not a vendor benchmark. Transfer time uses payload_kilobytes * 8 / bandwidth_mbps to estimate milliseconds (decimal KB = 1000 bytes; Mbps = 1000000 bits/s). Local paths use illustrative transfer fractions for reduced traffic. P95 and P99 use heuristic jitter multipliers, not measured distributions or guarantees. Cloud propagation uses about 0.005 ms per kilometer one way through fiber before routing, queuing, and service delay are added.
- Bandwidth changes transfer time more than propagation time.
- Distance changes propagation time even on a high-bandwidth link.
- Network load increases queueing and tail latency.
- Processing complexity can make edge slower than fog or cloud when local hardware is weak.
Quick reference
Use edge for immediate local action, fog for site-level coordination, cloud for fleet-level analysis, and hybrid when the action and record have different deadlines.