Open
Conversation
Design doc for a disk-backed inference cache that wraps inference.Client. Cache key is SHA-256 of JSON-serialized call parameters (model, system prompt, messages, options). Successful responses and truncations are cached. Transient errors are not. Motivated by observation strategy research: experimenting with different strategies means running the observe pipeline many times on the same conversations. The cache makes repeated calls free.
6c854a4 to
031f43b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Design doc and implementation for a disk-backed inference cache. The cache wraps
inference.Clientand stores responses keyed on the SHA-256 hash of the JSON-serialized call parameters (model, system prompt, messages, options). Cache hits return the stored response with no API call.Motivated by observation strategy research: experimenting with different presentation strategies (windowed, owner-only, adaptive) means running the observe pipeline many times on the same conversations. Without caching, each run pays full API costs for calls whose inputs have not changed.
Design highlights
ConverseOptionsdirectly, so new fields are automatically in the key--bucketconfiguration)--skip-cacheto bypass reads and writesDesign doc at
designs/012-inference-cache.md.Test plan
go test ./...passesmuse compose --limit 2, note cost. Run again, verify near-zero observe costls ~/.muse/cache/inference/shows sharded entries