Checkpoint: Worked Budgets; Quick Knowledge Check

Checkpoint: Worked Budgets; Quick Knowledge Check

animation
analytics-ml
edge-computing
TipData Dora, Data and analytics domain expertCheckpoint: Worked Budgets

You now know:

  • Cost, latency, and memory budgets must include the full pipeline, not only the model or gateway.
  • A failing latency requirement can decide the architecture before cost comparison starts.
  • Quantization, scheduling, and data reduction are practical levers for fitting edge hardware.

Concept Check

NoteQuick Knowledge Check

Q: When does edge computing save money versus cloud-only architecture?

Edge computing saves money when reduced data-transfer and cloud-processing costs exceed the gateway’s hardware, power, maintenance and operating costs; strict latency can justify edge investment even without net cost savings. For low-volume deployments (<1 GB/day), cloud-only is typically cheaper.

Q: Why can’t you rely on average latency alone when designing edge systems?

Cloud average latency might be 200 ms, but peak spikes can reach 2+ seconds during network congestion. Safety-critical systems must guarantee worst-case latency, not average latency. That’s why sub-100 ms requirements mandate edge processing.

Technical boundaries. The latency example uses a 200 ms cloud average and 2+ second peaks during network congestion. Its cost comparison requires reduced data-transfer and cloud-processing costs to exceed gateway hardware, power, maintenance and operating costs.

Back to the chapter