-
Notifications
You must be signed in to change notification settings - Fork 493
db: incorporate blob files into EstimateDiskUsage #4621
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
Comments
annrpom
added a commit
to annrpom/pebble
that referenced
this issue
May 7, 2025
This patch ensures that blob files are also included in disk usage estimation. Fixes: cockroachdb#4621
annrpom
added a commit
to annrpom/pebble
that referenced
this issue
May 8, 2025
This patch ensures that blob files are also included in disk usage estimation. Fixes: cockroachdb#4621
annrpom
added a commit
to annrpom/pebble
that referenced
this issue
May 8, 2025
This patch ensures that blob files are also included in disk usage estimation. Fixes: cockroachdb#4621
annrpom
added a commit
to annrpom/pebble
that referenced
this issue
May 8, 2025
This patch ensures that blob files are also included in disk usage estimation. Fixes: cockroachdb#4621
annrpom
added a commit
to annrpom/pebble
that referenced
this issue
May 9, 2025
This patch ensures that blob files are also included in disk usage estimation. Fixes: cockroachdb#4621
annrpom
added a commit
to annrpom/pebble
that referenced
this issue
May 13, 2025
This patch ensures that blob files are also included in disk usage estimation. Fixes: cockroachdb#4621
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
When estimating the disk usage between two bounds, we should incorporate contribution from blob files referenced from overlapping sstables. When there's partial overlap with a sstable, we don't have a means of accurately determining how much of a blob reference comes from the span passed into EstimateDiskUsage specifically. I suppose we could crudely estimate it using linear interpolation.
We use
(*sstable.Reader).EstimateDiskUsage(start, end)
to get an accurate estimate of the disk usage within the sstable itself. We divide that by theTableMetadata.Size
to get an estimate of the fraction of the table's blob references that fall within the range. Then for each blob reference, we scale the uncompressdValueLen
by that fraction to get estimates of the uncompressed value quantities. Then we scale each of those by the compression ratio of the blob file and sum them all together.Jira issue: PEBBLE-424
Epic CRDB-20379
The text was updated successfully, but these errors were encountered: