How a 48-Byte Payload Becomes a Fleet Bandwidth Problem
Ada re-derives this chapter’s own numbers step by step, at full precision
ADA · CALCULATION AUDIT
How a 48-Byte Payload Becomes a Fleet Bandwidth Problem
The chapter syncs one digital twin every 5 seconds at a 48-byte payload — a tiny 0.79 MB/day — then scales it to a fleet of 500 and reaches 395 MB/day. A payload small enough to look free becomes hundreds of megabytes once multiplied by a fleet and a cadence. This audit confirms the figures and shows how a 48-byte payload becomes a fleet bandwidth problem, and why cadence, not payload, is the real dial.
Companion to the chapter Lab: Build a Digital Twin — every number here comes from that chapter.
Ada: The sync-bandwidth panel above works one twin at a 5-second interval and a 48-byte payload. Let me confirm its figures, then show why the cadence knob matters more than the payload size.
For a single twin:
- Syncs per day:
86400 / 5 = 17,280 - Data per day:
17,280 x 48 = 829,440 bytes = 829,440 / 1,048,576 = 0.79 MB/day
Scale to the fleet of 500:
0.79 x 500 = 395 MB/day- Per month:
395 x 30 = 11,850 MB, which is about11.6 GBin binary units (the panel’s 11.8 counts a decimal gigabyte)
Now the lever. Bandwidth is 86400 / dt x S, so it scales inversely with the interval and only linearly with payload. Halving the payload from 48 to 24 bytes halves the load — but halving the interval from 5 s to 2.5 s also doubles it, and cadence is the term people reach for first when they want “fresher” twins. Tighten the interval fourfold, from 5 s to 1.25 s, and the same fleet climbs from 395 MB/day to about 1.58 GB/day.
The design meaning is that a payload small enough to look free — 48 bytes — still becomes hundreds of megabytes a day once multiplied by a fleet and a fast cadence, so sync interval, not payload, is the dial that decides whether raw twin telemetry can reach the cloud or must be aggregated at the edge first.
Every number above is taken from the chapter’s own material and re-derived step by step.