-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[opt](multi-catalog) Optimize remote scan concurrency. #51415
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](multi-catalog) Optimize remote scan concurrency. #51415
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
TPC-H: Total hot run time: 34374 ms |
TPC-DS: Total hot run time: 194476 ms |
ClickBench: Total hot run time: 29.22 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
Problem Summary: [opt] (multi-catalog) Optimize remote scan concurrency. 1. Use `ScannerScheduler::get_remote_scan_thread_num()` to replace `config::doris_scanner_thread_pool_thread_num` when calculate max scanners in the external table case. 2. Remove `parallel_scan_max_scanners_count` calculation logic.
Problem Summary: [opt] (multi-catalog) Optimize remote scan concurrency. 1. Use `ScannerScheduler::get_remote_scan_thread_num()` to replace `config::doris_scanner_thread_pool_thread_num` when calculate max scanners in the external table case. 2. Remove `parallel_scan_max_scanners_count` calculation logic.
Problem Summary: [opt] (multi-catalog) Optimize remote scan concurrency. 1. Use `ScannerScheduler::get_remote_scan_thread_num()` to replace `config::doris_scanner_thread_pool_thread_num` when calculate max scanners in the external table case. 2. Remove `parallel_scan_max_scanners_count` calculation logic.
Problem Summary: [opt] (multi-catalog) Optimize remote scan concurrency. 1. Use `ScannerScheduler::get_remote_scan_thread_num()` to replace `config::doris_scanner_thread_pool_thread_num` when calculate max scanners in the external table case. 2. Remove `parallel_scan_max_scanners_count` calculation logic.
Cherry-pick #51415 ### Check List (For Author) - Test <!-- At least one of them must be included. --> - [ ] Regression test - [ ] Unit Test - [ ] Manual test (add detailed scripts or steps below) - [ ] No need to test or manual test. Explain why: - [ ] This is a refactor/code format and no logic has been changed. - [ ] Previous test can cover this change. - [ ] No code files have been changed. - [ ] Other reason <!-- Add your reason? --> - Behavior changed: - [ ] No. - [ ] Yes. <!-- Explain the behavior change --> - Does this need documentation? - [ ] No. - [ ] Yes. <!-- Add document PR link here. eg: apache/doris-website#1214 --> ### Check List (For Reviewer who merge this PR) - [ ] Confirm the release note - [ ] Confirm test cases - [ ] Confirm document - [ ] Add branch pick label <!-- Add branch pick label that this PR should merge into -->
What problem does this PR solve?
Problem Summary:
Release note
[opt] (multi-catalog) Optimize remote scan concurrency.
ScannerScheduler::get_remote_scan_thread_num()to replaceconfig::doris_scanner_thread_pool_thread_numwhen calculate max scanners in the external table case.parallel_scan_max_scanners_countcalculation logic.Check List (For Author)
Test
set enable_profile=true; set profile_level=2;MaxScanConcurrency.Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)