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

Cache eviction and pinning #14

Open
kangas opened this issue Nov 28, 2016 · 0 comments
Open

Cache eviction and pinning #14

kangas opened this issue Nov 28, 2016 · 0 comments

Comments

@kangas
Copy link
Owner

kangas commented Nov 28, 2016

The initial cache implementation (#7) will likely just be a persistent key-value store with no eviction. Eventually, we'll have to evict cache entries.

Distinguish between:

  • TTL: how long the content should be considered "fresh"
    • Example: daily full index should be refetched after 24 hrs, and its derived artifacts (secondary indexes) regenerated
  • Date of recent use: for LRU eviction
  • Saved/pinned
    • Quarterly "full" indexes should not be evicted
    • User "starred" documents should not be evicted

Related reading:

https://r.va.gg/2013/10/should-i-use-a-single-leveldb-or-many-to-hold-my-data.html
https://r.va.gg/presentations/lxjs2013/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant