Skip to content
This repository has been archived by the owner on Aug 10, 2019. It is now read-only.

Reduce per-key metadata overheads #4

Open
vsreekanti opened this issue Jul 25, 2018 · 0 comments
Open

Reduce per-key metadata overheads #4

vsreekanti opened this issue Jul 25, 2018 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@vsreekanti
Copy link
Contributor

There are a few places in which we could reduce metadata overheads:

  • Instead of tracking key access frequencies for every single key in the database, we should instead use a heavy hitters sketch to track the most frequently accessed keys.
  • We shouldn't explicitly cache and materialize the replication factor for a key whose rep factor is the default rep factor.
  • Depending on how we use key sizes and what for, it might make sense to store a histogram of key sizes rather than every single size.
@vsreekanti vsreekanti added the enhancement New feature or request label Jul 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants