The average read response time is a much better performance metric, but is complicated in the presence of demotions and/or eviction-based reloading from disks. The inter-cache bandwidth usage is another important metric since many scenarios are bottle-necked by network resources [33]. It does appear that different policies would be optimal depending on which performance metric we use.
We now prove universal bounds for the single-path scenario as depicted in Figure 3 that simultaneously apply to both the average response time and inter-cache bandwidth metrics. The bounds apply to all algorithms irrespective of whether demotions, inclusion, or hints are used. Later, we explain extensions to compute the bounds for the multi-path scenarios as well.
![]() |
Cache at level ![]() ![]() |
![]() |
Size of the cache ![]() |
![]() |
Number of hits at ![]() |
![]() |
Avg. round-trip response time from ![]() |
![]() |
Avg. round-trip response time from disks |
![]() |
Sequence of reads seen by ![]() |
![]() |
Sequence of reads (misses) seen by disks |
![]() |
Number of demotions from ![]() ![]() |
From Figure 3 and definitions above, the total response time is
We define
to be the number of hits produced by Belady's offline OPT
policy on the request sequence
and a single-level cache of size
.