Skip to content

branch-4.0: [Opt](cloud) Add segment prefetcher #59482#61422

Open
bobhan1 wants to merge 3 commits intoapache:branch-4.0from
bobhan1:branch-4.0-pick-59482
Open

branch-4.0: [Opt](cloud) Add segment prefetcher #59482#61422
bobhan1 wants to merge 3 commits intoapache:branch-4.0from
bobhan1:branch-4.0-pick-59482

Conversation

@bobhan1
Copy link
Contributor

@bobhan1 bobhan1 commented Mar 17, 2026

pick #59482 and #60870

bobhan1 added 2 commits March 17, 2026 14:34
- Environment: 1 FE + 2 BE(aliyun,
[ecs.i4g.16xlarge](https://help.aliyun.com/zh/ecs/user-guide/instance-families-with-local-ssds#i4g),
2.7 GHz Intel® Xeon® Scalable (Ice Lake) processors with
high-performance local NVMe SSDs)
    - Network baseline bandwidth **32 Gbit/s** on each machine
- Duplicate table, 16 buckets, 6178831001 rows, data size is 396.837 GB
- Cold run means **query without any doris page, OS page cache or local
disk file cache, all data will be fetched from S3**.
- Query: `select count(user_id) from test_dup3 where env_id % 10 = 0 and
user_id%10=0 and time % 10 =0 and event_id % 10 = 0 and length(domain) %
10 = 0 and length(path) % 10 = 0 and length(query)%10=0;`
- For this query, each BE will download **114GB** data to local disk
file cache from S3
- 8 instance * 48 scanner = 384 scanner on each BE, and scanner thread
pool size is set to 48

||no prefetch|prefetch_block_size=2|
|---|---|---|
| query time | 2min47sec | 39sec273ms |
| network bandwidth</br>(on one BE) | <img width="960" height="720"
alt="slow"
src="https://github.com/user-attachments/assets/73a5d621-dc9c-4885-b336-9975230a40c9"
/>| <img width="960" height="720" alt="fast"
src="https://github.com/user-attachments/assets/0e147c4a-7b13-4eaa-a6ea-a8c171ce1c52"
/>|

based on apache#59476

- 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 -->

- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label <!-- Add branch pick label that this PR
should merge into -->
@bobhan1 bobhan1 requested a review from yiguolei as a code owner March 17, 2026 06:38
@hello-stephen
Copy link
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@bobhan1
Copy link
Contributor Author

bobhan1 commented Mar 17, 2026

run buildall

@bobhan1
Copy link
Contributor Author

bobhan1 commented Mar 17, 2026

run buildall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants