Copy the storage template by seeking between its data extents instead of scanning its whole logical size - #770
Open
BinSquare wants to merge 2 commits into
Open
Copy the storage template by seeking between its data extents instead of scanning its whole logical size#770BinSquare wants to merge 2 commits into
BinSquare wants to merge 2 commits into
Conversation
… of scanning its whole logical size, cutting packed run startup from ~11s to ~0.6s
…replaced across sparse layouts, large offsets and end-of-file data
BinSquare
force-pushed
the
binbin-sparse-copy-seek-data
branch
from
July 28, 2026 20:07
2eeab7a to
5517347
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 20 GiB storage template holds ~9 MiB of real data, but the copy read every chunk of its logical size to find that data, spending ~11s on the critical path of every packed run; using SEEK_DATA/SEEK_HOLE to jump between extents brings a warm
./app runfrom ~11.5s to ~0.6s, with a scan fallback for filesystems lacking the extension.