Skip to content
About
Main content
Model

When a cache entry pays

P/S is a natural batch size, with reuse count as the batch.

Read rate
the rate of reads on the object
Write rate
the rate of writes that invalidate it; summed over its dependencies
Cost to produce
the cost of computing one version
Saving
what serving one read from the cache saves
Reuse factor
reads per version

Recurring principle: Fixed cost per operation

How it behaves

One input on the horizontal axis, the others held fixed.

Data table
Reads per version by dependencies (20 reads/h, each input committed hourly)
Inputs the result depends onReuse factor R
120
1.2416.2
1.4813.6
1.7111.7
1.9510.3
2.199.14
2.428.25
2.667.51
2.96.9
3.146.37
3.385.93
3.615.54
3.855.19
4.094.89
4.334.62
4.564.38
4.84.17
5.043.97
5.283.79
5.513.63
5.753.48
5.993.34
6.223.21
6.463.09
6.72.99
6.942.88
7.172.79
7.412.7
7.652.61
7.892.54
8.132.46
8.362.39
8.62.33
8.842.26
9.072.2
9.312.15
9.552.09
9.792.04
102
10.31.95
10.51.9
10.71.86
111.82
11.21.78
11.41.75
11.71.71
11.91.68
12.21.64
12.41.61
12.61.58
12.91.55
13.11.53
13.31.5
13.61.47
13.81.45
14.11.42
14.31.4
14.51.38
14.81.35
151.33
15.31.31
15.51.29
15.71.27
161.25
16.21.23
16.41.22
16.71.2
16.91.18
17.11.17
17.41.15
17.61.13
17.91.12
18.11.1
18.31.09
18.61.08
18.81.06
19.11.05
19.31.04
19.51.02
19.81.01
201

Worked examples, recomputed

Every number the mechanisms quote for this relationship is recomputed from it, so none of them disagrees with it.

Where it appears

Each mechanism states it in its own names. The general symbol each name stands for is shown with it.

  • Caching

    What happens when we deliberately keep a second copy of data that no protocol forces to be correct?

    Read it in place →

  • Caching

    What happens when we deliberately keep a second copy of data that no protocol forces to be correct?

    Read it in place →