Keeping a Course Tutor's Retrieval Cache Fresh Under Latency Pressure
Caching in a course tutor that answers from PDFs should be treated as a retrieval design choice rather than an afterthought. The author recommends caching stable work such as parsed pages, chunks, and embeddings, while keeping final answer caches short-lived and linked to document versions. A common failure described is a tutor citing a replaced PDF, which dashboards miss because latency and index health look normal. The proposed fix is to attach document fingerprints and parser versions to cached data, expose cache age as a metric, and bypass answer caches when citation fingerprints no longer match the current course manifest. The article also notes that cache expiry thresholds must balance extra processing cost against stale material and may need to vary across subject areas.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in