Heterogeneous Cache Sizes
Not All Caches Are Equal
Real users have different cache budgets: a smartphone with 64 GB of free storage is different from a tablet with 500 GB. A smart-TV set-top box is different from a handheld. Even within a homogeneous fleet, users may pre-allocate storage differently. How does coded caching perform when cache sizes vary across users?
This section extends MAN to the heterogeneous-cache setting and quantifies the rate degradation from heterogeneity. The main result: at fixed aggregate cache , the best achievable rate is typically within a constant factor of the homogeneous rate at the average. Heterogeneity costs a factor of .
Definition: Heterogeneous-Cache Network
Heterogeneous-Cache Network
In a heterogeneous-cache coded caching network, user has cache size files, with . The average cache is . The aggregate caching gain is Demand vectors as in MAN.
At for all : reduces to homogeneous MAN. At extreme heterogeneity (some caches empty, others full): significantly different.
Theorem: Achievable Rate with Heterogeneous Caches
For a heterogeneous-cache network with per-user caches , the following rate is achievable: where is the average memory ratio. Moreover, the gap to the homogeneous rate at is at most a factor of 2.
A randomized placement that mimics MAN but allows cache sizes to vary achieves the stated rate. At aggregate level, the caching gain depends only on . Individual heterogeneity affects the distribution of cached content but not (to first order) the total coded-multicast opportunity.
Placement
User caches each subfile (in the MAN combinatorial structure, with ) with probability where is what user would cache under uniform MAN. Stated differently: each user caches a random subset of the MAN subfiles, with size proportional to its cache budget.
Delivery
Standard MAN XOR delivery, adapted to handle the randomness. Some XOR messages may need to be resent because not all expected subfiles are cached β this overhead is small on average.
Rate
Expected rate: matches MAN at up to a factor from the random admission. Worst case: at most 2Γ the homogeneous rate (Sengupta-Tandon-Clancy 2017, Theorem 1).
Heterogeneous Cache Effect
Rate as a function of cache heterogeneity (spread across users). At 0 (homogeneous): baseline MAN rate. As heterogeneity grows, some users cache more, others less β aggregate cache is fixed, rate slightly degrades. Even at full heterogeneity, gap to homogeneous is small. Reveals that average cache is the dominant quantity.
Parameters
Example: Two-Tier User Network
Design a network: 50% of users have (rich cache), 50% have (poor cache). Library , total users . Compute the achievable heterogeneous rate and compare with homogeneous MAN at .
Average
. .
Homogeneous rate
. files/round.
Heterogeneous rate
Rich users contribute more to coded multicast gain per cache bit. Achievable rate: approximately with small constant-factor gap. Rigorously: . Practically: -.
Engineering interpretation
A user with 10Γ the cache doesn't give 10Γ the benefit β the rate depends on aggregate cache, not max. For fair resource allocation: weighted proportional-to-budget works best. Rich users subsidize poor users through coded multicasting.
Rich Caches Subsidize Poor Caches
A subtle but important insight from the heterogeneous-cache analysis: users with larger caches not only benefit themselves (higher hit ratio, cache direct) but also contribute to other users' content via coded multicasting. A user with a very large cache holds many subfiles that appear in XOR messages targeting other users.
Economic implication: rich-cache users create positive externalities. In privacy-preserving / incentive-compatible designs, rewarding users who contribute large caches (beyond what they personally need) could improve total network performance. The theoretical basis for this is the MAN structure's sensitivity to aggregate cache rather than individual cache.
Common Mistake: Average, Not Minimum
Mistake:
Saying "heterogeneous MAN rate is bottlenecked by the smallest cache."
Correction:
The bottleneck is the aggregate cache, not the minimum. Rich caches compensate for poor caches in the coded-multicast gain formula. A single user with zero cache still receives coded messages that are XOR'd from other users' cached subfiles. Her own lack of cache reduces her hit rate but not the delivery rate to others.
Mathematically: depends on , not . This is a pleasant feature β fleet heterogeneity is surprisingly friendly to coded caching.