[IOTDB-5763] Optimize the memory estimate for INTO operations#9565
Merged
JackieTien97 merged 4 commits intomasterfrom Apr 12, 2023
Merged
[IOTDB-5763] Optimize the memory estimate for INTO operations#9565JackieTien97 merged 4 commits intomasterfrom
JackieTien97 merged 4 commits intomasterfrom
Conversation
|
SonarCloud Quality Gate failed. |
JackieTien97
approved these changes
Apr 12, 2023
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
When estimating the memory required for an INTO operation, always estimate the
select_into_insert_tablet_plan_row_limitrow data. When the number of sequences is large, a very scary memory size will be estimated.Now, we introduce
into_operation_buffer_size_in_byteto limit the maximum memory for INTO operations, and the maximum number of rows written will be dynamically adjusted.