Finite-Blocklength Coded Caching
Asymptotic Theory Meets Finite File Sizes
The MAN rate formula is an asymptotic result, proven as file size . For finite :
- Subpacketization overhead. Each file must be split into subfiles; indexing and header per subfile consume space.
- Error probability. Practical codes have non-zero decoding error; the rate achievable at error exceeds the asymptotic limit.
- Quantization and rounding. For non-integer , practical schemes round to nearest integer ; rounding increases rate.
The finite-blocklength (FB) regime is where theory meets practice. Understanding FB penalties is critical for realistic deployment assessments.
Theorem: Finite-Blocklength Rate Penalty
For coded caching with file size bits, cache size , users, and target error probability , the achievable rate is bounded by Penalties vanish as . For comparable to or smaller: significant penalty.
Two penalties: subpacketization and error-probability . Both scale as inverse square root of β standard finite-blocklength behavior.
Subpacketization penalty
subfiles, each of size . Header per subfile: . Total overhead: .
Error probability penalty
For target : add where is a channel dispersion constant.
Combined
Sum as dominant term: penalty when is small. When is large: subpacketization dominates.
Finite-Blocklength Rate Penalty vs File Size
Achievable rate vs file size. Penalty significant for small , asymptotically zero for large . Crossover at in bits.
Parameters
Practical Consequences of Finite Blocklength
The finite-blocklength analysis has concrete implications:
- Small files don't benefit much. A 10 KB web asset has bits. For , : β the subpacketization requirement dwarfs . No coded gain possible.
- Large files benefit. A 1 GB video chunk: . Same : plenty of room. Full gain achievable.
- Trade off for . If file size is fixed, increasing drives up, consuming file budget. Hence the emphasis on small in practice.
- PDAs (Ch 14) ease this. Polynomial-subpacketization schemes make for small . Reduces FB penalty for small files.
Deployment guidance: apply coded caching to videos (large files), not tiny web assets.
Example: Video vs Web: FB Analysis
Compare FB penalties for , : (i) video chunks (5 MB each), (ii) web assets (10 KB each).
Parameters
. subfiles.
Video chunks
MB bits. Per-subfile: bits. Too small β FB penalty severe.
Chunked differently
Reduce to 10: subfiles. Per-subfile: bits. Workable.
Web assets
KB bits. Per-subfile: bit. No coded gain possible.
Conclusion
Video at practical : good. Web at any : bad. Explains why production video CDNs are coded-caching candidates; web asset CDNs are not.
Theorem: PDA Reduces Finite-Blocklength Penalty
For a Placement Delivery Array (PDA) scheme with subpacketization for constant , the finite-blocklength penalty is reduced to β polynomial in rather than exponential.
PDAs avoid subpacketization in exchange for a slightly reduced multicasting gain. The net effect on FB performance is dramatic for practical .
PDA subpacketization
Graph-coloring-based delivery gives subfiles instead of .
FB scaling
Subpacketization penalty: . Polynomial decay; practically feasible for all meaningful .
Rate cost
PDA rate slightly worse than MAN's (factor 2 in worst case). Tradeoff: rate vs subpacketization.
Combined
At fixed : PDA achieves a usable rate; MAN fails to achieve its theoretical rate due to FB. PDAs practically "win" for deployable sizes.
Common Mistake: Asymptotic Rate Is Not Practically Achievable Below Threshold
Mistake:
Using the MAN asymptotic rate as the benchmark for practical performance without checking .
Correction:
The MAN formula is an upper bound on practically achievable rate in the finite-blocklength regime. For small or large , the achievable rate can be significantly higher than MAN's asymptotic value.
Always check: is ? If yes, MAN is approached. If no, use finite-blocklength analysis or PDA-based schemes.
Key Takeaway
Finite-blocklength penalties matter in practice. For small files or large , MAN's asymptotic gain is not achievable. PDA schemes (Ch 14) mitigate this. Video (large files) is the practical sweet spot; web assets (small files) are not. Fully characterizing the FB coded-caching capacity is an open problem with practical importance.