Tag Invalidation
A cache invalidation paradigm in which each entry is assigned tags and a mapping from tag to most recent invalidation timestamp is maintained. On read, the entry's write time is compared with the tag's invalidation timestamp to determine expiry, reducing the complexity of invalidation from O(number of entries) to O(number of tags).
Timeline (last 90 days)
Runtime Cache uses a tag invalidation mechanism: each cache entry records its tag and write time, and reads check the most recent invalidation timestamp for that tag; if the tag was invalidated after the entry was written, the entry is treated as expired.
Tag invalidation reduces invalidation operations from O(number of entries) to O(number of tags), requiring only a single timestamp update, but each read needs one extra timestamp check.
All Facts (2)
Runtime Cache uses a tag invalidation mechanism: each cache entry records its tag and write time, and reads check the most recent invalidation timestamp for that tag; if the tag was invalidated after the entry was written, the entry is treated as expired.
50%UnverifiedTag invalidation reduces invalidation operations from O(number of entries) to O(number of tags), requiring only a single timestamp update, but each read needs one extra timestamp check.
50%