Repository navigation
reusable_upload-file-s3: increase multipart chunk size - #147
Merged
Merged
Conversation
aws s3 cp uses 8 MiB parts by default, resulting in 92 to 289 write requests for each ccache archive. Use 256 MiB parts instead, reducing uploads to 3 to 10 requests while keeping retries limited to individual parts. Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
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
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.
By default, aws s3 cp uses 8 MiB multipart parts, so each 0.8 to 2.4 GB
ccache archive generates 92 to 289 billable write requests.
Use 256 MiB parts, which brings that down to 3 to 10. The largest archive
still fits the 10 requests the AWS CLI sends at once, so uploads stay
parallel and a failed part is retried alone.
A retried part now resends up to 256 MiB instead of 8 MiB.
Tested with AWS CLI 2.40.2 and S3Mock: a 512 MB file went up in two parts
and a 100 MiB file in a single PutObject. Not yet tested against R2.
cc: @Ansuel