Session-aware cache eviction uses information about conversations or agent tasks to decide which key-value cache entries should remain in scarce accelerator memory. A recently paused session may deserve retention because another turn is likely, even if newer unrelated requests have arrived.
The policy can combine recency, session state, prefix size, reuse probability and reconstruction cost. Poor eviction wastes memory or forces repeated prompt processing, so the optimal balance depends on traffic and available offload tiers.
