A fuzzy cache reuses expensive ML results without requiring exact request-key equality. This matters when inputs have a long tail and many requests are unique: even a small reduction in computation can save meaningful money. section 15.2.2
Relaxed matching can be implemented at increasing levels of aggressiveness:
- Match cache keys against regular expressions so one result serves multiple similar requests. section 15.2.2
- Match keys by semantic similarity, as in GPTCache-style caching for LLM queries. section 15.2.2
- Treat fuzziness as a reliability risk: relaxed matching increases the chance of false cache hits. section 15.2.2
When exact repetition is rare
A search or language-model service may receive mostly unique requests within a cache lifetime. A regex-based or semantic cache can still share selected results, but only when mistaken reuse is acceptable. section 15.2.2
