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 (M,R)(M, R) plane bounded above by MAN and below by cut-set. The width of this envelope is the slack: the unknown region where Rβˆ—(M)R^*(M) might lie.

A natural question is: what is the multiplicative gap RMAN/Rcut-setR_{\text{MAN}}/R_{\text{cut-set}}? 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 K,Nβ‰₯1K, N \geq 1 and M∈[0,N]M \in [0, N], RMAN(M)Rβˆ—(M)β€…β€Šβ‰€β€…β€Š12.\frac{R_{\text{MAN}}(M)}{R^*(M)} \;\leq\; 12. 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 1+KM/N1 + KM/N is correct up to a constant factor, which in most practical regimes is much less than 12.

MAN Gap vs. Cut-Set

The multiplicative gap RMAN/Rcut-setR_{\text{MAN}}/R_{\text{cut-set}} as a function of M/NM/N. Horizontal reference lines show the MN '14 proven bound (gap ≀12\leq 12) 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 K,NK, N. The plot reveals where the cut-set bound is slack (large gap) and where it is nearly tight (gap β‰ˆ1\approx 1).

Parameters
20
40

Definition:

Number of Distinct Demands

Given a demand vector d=(d1,…,dK)\mathbf{d} = (d_1, \ldots, d_K), let Ne(d)β€…β€Š=β€…β€Šβˆ£{d1,d2,…,dK}∣N_e(\mathbf{d}) \;=\; |\{d_1, d_2, \ldots, d_K\}| denote the number of distinct demands. We have 1≀Ne(d)≀min⁑(K,N)1 \leq N_e(\mathbf{d}) \leq \min(K, N).

Worst-Case Demands: All Distinct

For the MAN scheme, the worst-case rate is achieved when Ne(d)=min⁑(K,N)N_e(\mathbf{d}) = \min(K, N) β€” all users request distinct files (if K≀NK \leq N), or every file is requested at least once (if K>NK > N). 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 d\mathbf{d} only through Ne(d)N_e(\mathbf{d}) and equals RMAN(M,Ne)R_{\text{MAN}}(M, N_e), monotone in NeN_e.

This is why the "worst-case" definition of Rβˆ—(M)R^*(M) 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 Ne(d)N_e(\mathbf{d}). Worst case is Ne=min⁑(K,N)N_e = \min(K, N); 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
10
20
0.2

Example: Gap Analysis: K=3K = 3, N=3N = 3

For K=N=3K = N = 3, compute RMAN(M)R_{\text{MAN}}(M) and the cut-set lower bound for M∈{0,1,2,3}M \in \{0, 1, 2, 3\}. Quantify the gap.

What the Gap Tells Us

The example above shows the cut-set bound is often tight at the endpoints (M=0M = 0 and M=NM = N) but loose in the middle. Why? The middle region Mβ‰ˆN/Kβ‹…tM \approx N/K \cdot t for moderate tt 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 Rβˆ—R^* is bounded below by cut-set. (ii) Scaling structure: the cut-set bound has the form s(1βˆ’sM/N)s(1 - sM/N), which suggests the general shape of Rβˆ—R^* as a function of MM. 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.