Cache extensions for async functions#1376
Open
TristonianJones wants to merge 1 commit into
Open
Conversation
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.
Add CachedBinding with a pluggable Cache/StaleCache backend, a default
bounded cache, configurable key function, and stale-while-error /
stale-while-revalidate behavior. Errors are not cached.
The default key function keys on string and bool arguments only and
declines to cache calls with numeric or complex arguments (those use a
richer notion of equivalence than a string key can capture safely);
callers needing such caching supply CacheKeyFunc or CustomCache.
The default cache is bounded and TTL-aware, using CLOCK (second-chance)
eviction rather than a strict LRU so that reads do not mutate shared
ordering state: a Get takes only a read lock and sets a per-entry atomic
referenced bit, allowing reads to proceed concurrently, while only Set and
the eviction it triggers take the exclusive lock. The configured size is
respected exactly, and evicting an entry only costs a recomputation on its
next access.