The Bandwidth-Budget Equations

The Bandwidth-Budget Equations

Ada checks the bandwidth-budget equations — byte rate, reduction ratio, and queue stability

ADA · CALCULATION AUDIT

Foundations · optional mathematics and physics

The Bandwidth-Budget Equations

This chapter frames bandwidth as conservation of bytes over time — production, reduction, upload, and storage must share one unit before a gateway claim is accepted, starting from a 5-minute (300 s) review window. Because the text gives no fixed payload sizes or link rates, the audit keeps its terms symbolic instead of inventing values. This audit lays out the bandwidth-budget equations — byte rate, reduction ratio, and queue stability — as reusable checks.

Companion to the chapter Bandwidth Optimization at the Edge — every number here comes from that chapter.

Byte rate, reduction ratio, and queue stability, no invented constants

Bandwidth math is conservation of bytes over time: production, reduction, upload, and storage must use the same units before a gateway claim is accepted.

See the relationship before changing it

The figure reads from left to right. The blue card is review window. The middle card applies this page's rule. The green card is review-window duration. Walk the arrows once: set the input, apply the rule, then read the result with its unit.

The retained audit below checks several chapter fixtures. This model keeps those stated values fixed and changes only review window, so the numeric fixture does not switch without explanation.

Walk the arrows. A longer review window accumulates more produced bytes at any fixed source rate.

Derive the baseline in four named moves

1. 1

   Name the input. The chapter baseline is 5 min.

2. 2

   Name the relationship. window seconds = minutes x 60 s per minute

3. 3

   Substitute with units. 5 min x 60 s/min = 300 s

4. 4

   Read the result. Keep the unit beside the value. Use it only inside the technical boundary on this page.

Predict, then change review window

Try Predict the direction of window seconds = minutes x 60 s per minute. Test another review window, then compare review-window duration.

Review window

5 min

Chapter baseline

Review-window duration

Observe A longer review window accumulates more produced bytes at any fixed source rate. Reset review window to 5 and compare review-window duration.

Explain A longer review window accumulates more produced bytes at any fixed source rate.

Check yourself

What should you do before trusting a moved-control result?

Answer: Predict its direction, apply the shown relationship, keep the units, and reset to the worked baseline.

What does this small model leave out?

Answer: Only review window moves here. Field effects named in the technical boundary stay fixed.

Honesty note. This teaching model changes only review window. It is not a field prediction.

TryThis chapter frames bandwidth as conservation of bytes over time — production, reduction, upload, and storage must share one unit before a gateway claim is accepted, starting from a 5-minute ( 300 s ) review window. Use Check derivation.

ObserveThe displayed ledger resolves 5-minute, 300 s at full precision. This audit lays out the bandwidth-budget equations — byte rate, reduction ratio, and queue stability — as reusable checks. Check derivation shows this.

ExplainQueue growth is the signed difference between incoming and outgoing byte rates: positive growth consumes the outage buffer, while a zero or negative balance keeps the uplink stable under the stated traffic window. Check derivation confirms it.

The working

1. Convert the chapter's review window first. The text gives a five-minute summary example but no fixed payload sizes or link rates, so this audit keeps payload and capacity terms symbolic instead of inventing values.

T_window = 5 min x 60 s/min = 300 s

2. Count raw and reduced traffic in bytes per second. If a gateway receives N samples of S_raw bytes during the same window, the raw production rate is:

R_raw = (N x S_raw) / T_window

Review question	Formula to verify	Audit result
Window conversion	5 min x 60 s/min	300 s. The time unit is explicit before any byte-rate calculation. arithmetic verified
Reduction ratio	reduction = 1 - (B_reduced / B_raw)	Both byte totals describe the same window, so the ratio is dimensionless and can be reported as a percentage with 100 x reduction.
Stable uplink	R_reduced + R_urgent <= C_uplink	Reduced routine traffic and urgent traffic must be compared with link capacity in the same bytes-per-second unit.
Backpressure growth	Q_growth = R_in - R_out	When incoming bytes per second exceed outgoing bytes per second, the queue grows; when the value is zero or negative, it is stable.
Outage storage	Q_needed = Q_start + max(0, Q_growth) x T_outage	The storage claim is valid only if the retained queue budget is at least the starting backlog plus positive growth over the outage time.

3. The physics check is unit consistency. A bandwidth design cannot compare samples per window, bytes per message, and cellular capacity until they are converted into compatible byte totals or byte rates. That is why the accepted record must name the window, payloads, urgent bypass, queue limit, expiry rule, and loss marker.

4. The design decision follows the sign of the queue balance. If R_reduced + R_urgent fits under C_uplink, the link can carry the accepted traffic mix under the stated conditions. If it does not, the review must change the reduction rule, priority policy, retention limit, or tier placement. No payload-size or link-rate number is claimed here because the chapter does not supply one.

Technical boundaries
These bandwidth equations deliberately do not simulate burst arrivals, packet loss, contention, framing, retries, or variable compression; they are conservation checks for byte production and service rates over one common window.

Work the audit first, then check the displayed derivation.

Every number above is taken from the chapter's own bandwidth-budget example and re-derived step by step.