[fix](flush) Fix the issue of incorrect calculation of the number of flush threads in cloud mode#59524
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
|
run buildall |
TPC-H: Total hot run time: 32208 ms |
TPC-DS: Total hot run time: 173729 ms |
ClickBench: Total hot run time: 27.28 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run buildall |
TPC-H: Total hot run time: 32012 ms |
TPC-DS: Total hot run time: 172014 ms |
ClickBench: Total hot run time: 27.62 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run buildall |
TPC-H: Total hot run time: 31360 ms |
TPC-DS: Total hot run time: 174737 ms |
ClickBench: Total hot run time: 26.94 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run buildall |
|
PR approved by at least one committer and no changes requested. |
TPC-H: Total hot run time: 31525 ms |
TPC-DS: Total hot run time: 176917 ms |
ClickBench: Total hot run time: 27.16 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run buildall |
TPC-H: Total hot run time: 31555 ms |
TPC-DS: Total hot run time: 173148 ms |
ClickBench: Total hot run time: 26.69 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
…e number of flush threads in cloud mode apache#59524 (apache#60082) Cherry-picked from apache#59524 Co-authored-by: Refrain <113875799+0AyanamiRei@users.noreply.github.com>
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx #38789
Problem Summary:
In cloud mode, use cache disk count instead of data disk count. So in cloud mode the
ExecEnv::GetInstance()->storage_engine().get_disk_num()is default 0Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)