Support expiring cache use callback#79
Open
yigongliu-concur wants to merge 18 commits intohashicorp:mainfrom
Open
Support expiring cache use callback#79yigongliu-concur wants to merge 18 commits intohashicorp:mainfrom
yigongliu-concur wants to merge 18 commits intohashicorp:mainfrom
Conversation
…make XXXCache just thread-safe wrapper over XXXLRU, avoid NoLock ugliness
bay1ts
approved these changes
Jan 14, 2022
bay1ts
approved these changes
Jan 14, 2022
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.
support simple expiring caches backed by eviction logic of existing 2q, arc and simple lru:
NewExpiring2Q(size int, expirationTime time.Duration)
NewExpiringARC(size int, expirationTime time.Duration)
NewExpiringLRU(size int, expirationTime time.Duration)
no changes to existing api, no client code change if not using expiring cache.
client code can register callback to receive evicted/expired keys/vals.
there are 2 expiring policies similar to Guava's CacheBuilder (https://guava.dev/releases/19.0/api/docs/com/google/common/cache/CacheBuilder.html): ExpireAfterWrite and ExpireAfterAccess
the default cleanup of expired entries is lazy, only when space is needed for new entries (inside Add) or accurate keys (inside Keys) and size (inside Len) are needed; can add background cleanup by a goroutine periodically calling RemoveAllExpired()
following same pattern of simple LRU, separate 2q/arc Cache from LRU, so that XXXCache is just a thread safe wrapper of XXXLRU. this avoids the double locking when ExpiringCache wraps 2Q or ARC.