-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[opt](scan) Release instances of Segment to avoid consuming a large amount of memory in ParallelScannerBuilder #44189
Conversation
…mount of memory in ParallelScannerBuilder
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
TeamCity be ut coverage result: |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
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.
LGTM
…mount of memory in ParallelScannerBuilder (#44189) For wide tables, a loaded Segment will consume a large amount of memory, so it is necessary to release instances of `Segment` as soon as possible.
…ng a large amount of memory in ParallelScannerBuilder #44189 (#44445) Cherry-picked from #44189 Co-authored-by: Jerry Hu <[email protected]>
…mount of memory in ParallelScannerBuilder (apache#44189) For wide tables, a loaded Segment will consume a large amount of memory, so it is necessary to release instances of `Segment` as soon as possible.
What problem does this PR solve?
For wide tables, a loaded Segment will consume a large amount of memory, so it is necessary to release instances of
Segment
as soon as possible.Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)