Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-architect the cache mechanism to track max_size, max_age and cull_freq #14

Closed
saurabh0719 opened this issue May 15, 2021 · 0 comments · Fixed by #15
Closed

Re-architect the cache mechanism to track max_size, max_age and cull_freq #14

saurabh0719 opened this issue May 15, 2021 · 0 comments · Fixed by #15
Assignees
Labels
enhancement New feature or request

Comments

@saurabh0719
Copy link
Owner

Description :

  • Update the architecture to maintain an access list (using the LRU) to set default max_age of the cache and track max_age of each individual key-value pair.
  • Also track the max_size of the cache and allow the user to set the default cull_freq (cull frequency - percentage of key-value pairs to be deleted when cache reaches it's max_size)
  • Update cache (resolve max_age and LRU) after every operation. (set, get etc. etc.)
  • Allow set() to take individual max_age for key-value pairs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant