The Memory-Load Envelope and the Gap
Quantifying the Gap
With the MAN upper bound and the cut-set lower bound in hand, we can plot the memory-load envelope β the region in the plane bounded above by MAN and below by cut-set. The width of this envelope is the slack: the unknown region where might lie.
A natural question is: what is the multiplicative gap ? Maddah-Ali and Niesen proved it is at most 12; later analyses reduced it to 4 (under coded placement) and exactly 1 (under uncoded placement, YMA 2018). This section quantifies the gap and discusses what it tells us about the structure of the problem.
Theorem: Order-Optimality of MAN
For all and , In particular, the MAN scheme is order-optimal: it achieves a rate within a constant factor of any possible scheme's rate.
Order-optimality is a weaker but still very useful statement: the MAN scheme's rate cannot be more than a constant factor above the true optimum. This is the kind of guarantee that lets systems engineers deploy MAN-like schemes confidently: the asymptotic gain is correct up to a constant factor, which in most practical regimes is much less than 12.
Three regimes for $M$
Split into three regimes based on how compares to : (i) (small ), (ii) , (iii) .
Small $M$ regime
For small , . Cut-set with : , which is approximately for small . Gap: constant .
Intermediate $M$ regime
Use cut-set with for . After some algebra, the gap is bounded by a constant (this is the delicate part of the MN '14 proof).
Large $M$ regime
For , both and the cut-set bound are near zero; the gap is bounded by a constant.
Take max
Maximum multiplicative gap across all regimes is 12. (The number 12 was later improved in subsequent works; it is not tight, but it suffices to establish order-optimality.)
MAN Gap vs. Cut-Set
The multiplicative gap as a function of . Horizontal reference lines show the MN '14 proven bound (gap ) and the YMA '18 tight result (gap = 1 under uncoded placement). The gap is typically much smaller than 12 β maxing around 2β3 for typical . The plot reveals where the cut-set bound is slack (large gap) and where it is nearly tight (gap ).
Parameters
Definition: Number of Distinct Demands
Number of Distinct Demands
Given a demand vector , let denote the number of distinct demands. We have .
Worst-Case Demands: All Distinct
For the MAN scheme, the worst-case rate is achieved when β all users request distinct files (if ), or every file is requested at least once (if ). Intuitively, when demands coincide, the server can exploit the coincidence to reduce the number of distinct subfiles to deliver. The rigorous statement: for MAN delivery, the rate depends on only through and equals , monotone in .
This is why the "worst-case" definition of focuses on distinct demands: they maximize over all demand vectors.
Rate vs. Number of Distinct Demands
The MAN rate as a function of the number of distinct demands . Worst case is ; easier demand vectors (many coincidences) allow strictly lower rate. This reveals a fundamental averaging question: the MAN worst-case rate is not the average-case rate, and the gap between them is the subject of research in non-uniform demand regimes (Chapter 13).
Parameters
Example: Gap Analysis: ,
For , compute and the cut-set lower bound for . Quantify the gap.
MAN rates
. . So: ; ; ; .
Cut-set bounds
. : . : . : . Max over : : max(1, 2, 3) = 3. : max(2/3, 0, 0) = 2/3. : max(1/3, -2, -3) = 1/3. : 0.
Gap ratios
: 3/3 = 1 (tight!). : 1/(2/3) = 1.5. : (1/3)/(1/3) = 1 (tight!). : 0/0 (undefined). The cut-set bound is tight at and , but loose at . MAN exceeds the cut-set by factor at .
What the Gap Tells Us
The example above shows the cut-set bound is often tight at the endpoints ( and ) but loose in the middle. Why? The middle region for moderate is where the coded multicasting gain is most pronounced; the cut-set bound does not capture this gain directly β it is a joint-entropy argument that does not distinguish between uncoded and coded schemes.
The YMA '18 converse (next section) fills this gap by using a more refined information-theoretic argument that explicitly accounts for uncoded placement structure. Under general (coded) placement, the gap-closing remains open.
Common Mistake: A Bound Can Be Loose Without Being Useless
Mistake:
Dismissing the cut-set bound because it is not tight: "MAN is order-optimal, so who cares about the converse?"
Correction:
Even a loose converse serves two purposes: (i) No-go result: the converse tells us no scheme can do strictly better than the bound. Even if MAN is not optimal, the true is bounded below by cut-set. (ii) Scaling structure: the cut-set bound has the form , which suggests the general shape of as a function of . MAN also has this shape. The coincidence is not accidental.
More refined converses β YMA '18 and beyond β build on the cut-set bound, tightening it with additional information-theoretic constraints.