Skip to content

branch-3.1: [enhance](compaction) optimize mow base compaction parameters #52321 #52606

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.

Sign up for GitHub

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

Jump to bottom
Merged
morrySnow merged 1 commit into from
Jul 2, 2025
Merged

branch-3.1: [enhance](compaction) optimize mow base compaction parameters #52321 #52606

morrySnow merged 1 commit into from
Jul 2, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jul 1, 2025

Cherry-picked from #52321

@luwei16
[enhance](compaction) optimize mow base compaction parameters (#52321)
ec77f70 
## 1 Increase base compaction frequency
In high-frequency mow load scenarios, the default two-hour compaction
interval is too long, causing the compaction score to rise. Therefore,
adjust base_compaction_freeze_interval_s from two hours to 30 minutes.

## 2. Increase the limit on compaction score per run
The base_compaction_max_compaction_score parameter limits the number of
rowsets in a single compaction to control memory usage. However, in
high-frequency mow load scenarios, this can slow down compaction and
prevent it from keeping up with data growth. Thus, this parameter is
increased to 200.
@github-actions github-actions bot requested a review from morrySnow as a code owner July 1, 2025 13:04
@Thearas
Copy link
Contributor

Thearas commented Jul 1, 2025

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?

@dataroaring dataroaring closed this Jul 1, 2025
@dataroaring dataroaring reopened this Jul 1, 2025
@Thearas
Copy link
Contributor

Thearas commented Jul 1, 2025

run buildall

@hello-stephen
Copy link
Contributor

hello-stephen commented Jul 1, 2025

BE UT Coverage Report

Increment line coverage 50.00% (5/10) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 45.05% (12380/27480)
Line Coverage 36.04% (109621/304123)
Region Coverage 35.12% (56811/161760)
Branch Coverage 32.24% (30813/95578)

@morrySnow morrySnow merged commit 55187ab into branch-3.1 Jul 2, 2025
19 of 22 checks passed
@github-actions github-actions bot deleted the auto-pick-52321-branch-3.1 branch July 2, 2025 05:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@morrySnow morrySnow morrySnow approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@Thearas @hello-stephen @morrySnow @dataroaring @luwei16