When should you run inference on-device instead of in the cloud?
When latency must be predictable, connectivity is unreliable, or the data should not leave the device. Otherwise the cloud is cheaper and easier to update.
Read the full answer →Running models on-device — latency, power, and the trade-offs against cloud.
When latency must be predictable, connectivity is unreliable, or the data should not leave the device. Otherwise the cloud is cheaper and easier to update.
Read the full answer →Small enough to fit the NPU's on-chip memory after quantisation — on microcontroller-class parts that means single-digit megabytes, which is an architecture constraint, not a compression one.
Read the full answer →On-device handles the perception loop and anything latency-bound; the cloud handles long-horizon reasoning and persistent memory. The split follows the latency budget.
Read the full answer →Sub-10 ms per frame for vision-transformer inference on current mobile and embedded accelerators, which is enough for a real-time interaction loop.
Read the full answer →