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

Reduce per-key metadata overheads #4

Open
@vsreekanti

Description

@vsreekanti

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.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions