vmware / vmware/splinterdb

Investigate and prototype interfaces to externalize space usage and related metrics

Open
#166 0 comments 0 reactions 1 assignee View on GitHub

@gapisback is already working on this.

Since Dec 3, 2021.

enhancement
Dominant language
C
Stars
732
Forks
67
PR merge metrics
No merged PRs in 30d

Description

This is an umbrella feature request to productize and externalize existing internal methods that track space usage and related metrics. It's likely that we may need to add a few more metrics, but here is an initial straw man list.

  1. Total space of the device
  2. Total allocated space; i.e. space consumed by all allocated extents
  3. Total used / unused space; i.e. space actually used / still free by pages in allocated extents
  4. Total free space; i.e. space left-over in unallocated extents
  5. Number of extents allocated
  6. Data v/s log space consumption; allocated, used / unused etc.
  7. Quick summary of row-counts: # of rows inserted

Some of these ideas have been aired out in this internal slack post. Feedback suggests that these are useful and do-able.

Investigate and prototype how-to extend upcoming splinterdb-cli to provide interfaces to report such metrics.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.