-
Notifications
You must be signed in to change notification settings - Fork 206
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
fscache: fix large stargz chunks processing #546
Conversation
Tested OK with fscache backend and ghcr.io/stargz-containers/wordpress:5.9.2-esgz ! |
88f0e43
to
0fe072a
Compare
Ensure that the stargz chunks in the blob meta are sorted by uncompressed_offset and ordered by chunk index so that they can be found quickly at runtime with a binary search. Signed-off-by: Yan Song <yansong.ys@antfin.com>
@imeoer , your pull request has been updated. A new test job will be submitted. Please wait in patience. |
@imeoer , the test job has been submitted. Please wait in patience. |
1. use blob_compressed_size to compute stargz's compressed gzip_size; 2. use binary search to find stargz chunk (sorted by uncompressed_offset in blob meta); Signed-off-by: Yan Song <yansong.ys@antfin.com>
0fe072a
to
87fdc00
Compare
@imeoer , your pull request has been updated, but no change is detected in the code. |
@imeoer , The CI test is completed, please check result:
Congratulations, your test job passed! |
@imeoer can we highlight this feature in |
I think they can be in another PR, let's fix the break first. |
builder: sort stargz chunks by uncompressed_offset
fscache: some fixups for large stargz chunk
Signed-off-by: Yan Song yansong.ys@antfin.com