fix streamloader use too much memory #19
Merged
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
sollhui
force-pushed
the
fix_memory_too_large
branch
from
4861663 to
1d3e57c
Compare
sollhui
changed the title
Closed
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.
close apache/doris#36119
When using streamloader to load a file of 400G to weigh table(1500 column), the tool streamloader uses too much memory which causes oom-kill.
Why this happened is that read space is faster than Doris load space, so lots of data stay in memory and cause OOM.
The PR to reduce the queue size to solve this problem.
Test result(32 core 64G memory)
The tool only uses 0.4% memory