request-coalescing · research · also Cache request coalescing

Request coalescing (cache)

Cache request coalescing combines compatible pending requests for the same object behind one in-flight fetch instead of issuing duplicate backend fetches.

Related Observatory article: Request coalescing (cache) on hesela.com

The delayed-hit model allows one outstanding fetch per object and associates later pending requests with it. They are released when the object becomes available. This reduces duplicate fetches within that model; it does not make a pending request a resident hit. [1]

Use a key that identifies the same permitted representation and validity requirements. The single immutable-object example has no writes or invalidations and does not establish correctness for mutable data or caller-specific responses. [2]

Relations

related
Delayed cache hit, Cache admission, SIEVE cache eviction

Citations

  1. Keren et al. Latency-Aware Caching with Delayed Hits: From Bursty Traffic to Pipeline Architectures. NSDI 2026, sections 1.1 and 4. (accessed 2026-10-19)
  2. Hesela: request-coalescing assumptions in the single-object delayed-hit example. (accessed 2026-10-20)

JSON: /data/terms/request-coalescing.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Request coalescing (cache). Hesela. 2026-10-20. https://hesela.dev/terms/request-coalescing/