-
Notifications
You must be signed in to change notification settings - Fork 3.9k
[improvement](be) Add CPU-aware S3 rate limiter #65420
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
Open
0AyanamiRei
wants to merge
14
commits into
apache:master
Choose a base branch
from
0AyanamiRei:feature/cpu-aware-s3-limiter
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
c2ffc30
[feature](be) Add CPU-aware S3 rate limiter configurations
0AyanamiRei a4bc63e
Rename token_per_second_max to s3_token_per_second_max for consistency
0AyanamiRei 90a3236
[feature](be) Centralize S3 rate limiter config calculation
0AyanamiRei e48dfcf
[refactor](be) Use effective config for S3 rate limiter initializatio…
0AyanamiRei d529f3f
[test](be) Add unit tests for get_effective_s3_rate_limiter_config
0AyanamiRei e1eb6f9
refactor: Use S3RateLimiterConfigGuard in s3_rate_limiter test
0AyanamiRei 0a221da
[test](be) Add unit tests for S3 rate limiter dynamic rebuild with pe…
0AyanamiRei 1a1d991
[test](be) Assert get_limit() in S3 GET limiter cap-change rebuild test
0AyanamiRei 85ba22a
[test](be) Fix stale config comment and add absolute PUT mode test
0AyanamiRei a4effbe
[fix](be) Guard CPU-aware S3 limiter overflow
0AyanamiRei 46d20ea
remove
0AyanamiRei c614307
add
0AyanamiRei f6a3d0f
[improvement](be) Align S3 bandwidth limiter handling
0AyanamiRei 72fcefa
rw
0AyanamiRei 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
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.
The byte limiter only gets charged on the native S3 path. Azure still uses the same
enable_s3_rate_limiter/S3ClientFactory::rate_limiter()helper, but itsput_object,upload_part, andget_objectcalls never passstream.size()orbytes_readthroughbytes_rate_limiter(). With the new positive defaults fors3_get_bytes_per_second_per_coreands3_put_bytes_per_second_per_core, enabling the rate limiter now throttles S3 bandwidth but silently leaves Azure bandwidth unlimited. Please either apply the same byte accounting to the Azure read/write helpers or make these new configs/API explicitly S3-native so Azure users do not expect them to apply.