-
Notifications
You must be signed in to change notification settings - Fork 20
feat: optimize S3 cache performance with batch operations and increased workers #278
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
Merged
+357
−67
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to worry about large buckets with so many objects that we run into scalability issues?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The concern is valid for very large buckets, but:
ListObjectsfails or times out, it falls back to sequentialIt feels like a bucket would need 100k+ objects before this becomes problematic, and even then the 60s timeout provides a safety net
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the S3 bucket lacks a retention policy and grows unbounded, there are two options.
Option 1 (recommended): Add a retention policy to the bucket.
This is the proper fix. Old cache artifacts should be cleaned up periodically.
Option 2: Add a
maxListPagessafeguard.If a retention policy isn't possible, we can limit pagination to avoid memory issues with very large buckets:
Behavior:
For a build with 100 packages against a 50k object bucket:
This caps memory at ~1MB while preserving the optimization for reasonably-sized buckets.
In any case, I feel this is a bit of a premature optimization (given the option 1 is faster/smarter to apply) that in any case would be better suited for a follow-up PR.