-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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](routine-load) optimize routine load task allocation algorithm #34778
Conversation
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
5b9e6b7
to
d55ed99
Compare
d55ed99
to
c7f0641
Compare
run buildall |
TPC-H: Total hot run time: 41060 ms
|
TPC-DS: Total hot run time: 187205 ms
|
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
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
TPC-DS: Total hot run time: 185241 ms
|
ClickBench: Total hot run time: 30.62 s
|
run performance |
The current task allocation algorithm takes into account the cache information of the object pool. If there are still more than half of the idle slots in the previously executed BE, they will be allocated to the previous BE.
However, in the actual process of execution in the production environment, there have been serious imbalances.
So we optimized the algorithm based on the following reasons: