You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 10, 2019. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
There are a few places in which we could reduce metadata overheads:
The text was updated successfully, but these errors were encountered: