[cherry-pick][core] Fix the GCS memory usage high issue (picks #32302) #32330
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
It's not because of leak. The root cause is because we allocate more requests when start. This PR fixed it by making the number of call constant.
…ct#32323) This is a corner case where buffer could be 0 and a comments needs to be fixed in the previous PR.
zhe-thoughts
changed the title
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.
This cherry-picks #32302
Why are these changes needed?
It's not because of leak. The root cause is because we allocate more requests when start. This PR fixed it by making the number of call constant.
Related issue number
Checks
git commit -s) in this PR.scripts/format.shto lint the changes in this PR.