remove QUEUE_TIMEOUT_GET, use a Stop sentinel instead #551
Conversation
This file contains 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
|
Merged, thanks for the PR! |
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.
The QUEUE_TIMEOUT_GET causes some unnecessary slowdowns. By removing it and using a sentinel instead to end the threads, several s3-based operations can run faster.
Old:
% time aws s3 cp empty_file s3://test_bucket/empty_file
upload: ./empty_file to s3://test_bucket/empty_file
aws s3 cp empty_file s3://test_bucket/empty_file 0.31s user 0.05s system 16% cpu 2.189 total
New:
% time aws s3 cp empty_file s3://test_bucket/empty_file
upload: ./empty_file to s3://test_bucket/empty_file
aws s3 cp empty_file s3://test_bucket/empty_file 0.27s user 0.06s system 85% cpu 0.385 total