We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The current implementation of ZTOC building first creates zinfo from the layer file, then creates a toc from the file:
soci-snapshotter/ztoc/ztoc_builder.go
Lines 93 to 101 in 99fc201
The implentation of Zinfo building first creates the Zinfo from the layer file, then gets span digests from the file.
soci-snapshotter/ztoc/zinfo_builder.go
Lines 40 to 54 in 99fc201
The full path for compressed layers is:
We read the file 3 times and decompress it 2 times.
We should be able to do this in a streaming context:
That way we should be able to read the file once, decompress once, and read the uncompressed stream once.
No response
Related to: #366 #76
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
The current implementation of ZTOC building first creates zinfo from the layer file, then creates a toc from the file:
soci-snapshotter/ztoc/ztoc_builder.go
Lines 93 to 101 in 99fc201
The implentation of Zinfo building first creates the Zinfo from the layer file, then gets span digests from the file.
soci-snapshotter/ztoc/zinfo_builder.go
Lines 40 to 54 in 99fc201
The full path for compressed layers is:
We read the file 3 times and decompress it 2 times.
Describe the solution you'd like
We should be able to do this in a streaming context:
That way we should be able to read the file once, decompress once, and read the uncompressed stream once.
Describe any alternative solutions/features you've considered
No response
Any additional context or information about the feature request
Related to:
#366
#76
The text was updated successfully, but these errors were encountered: