[Enhancement] adjust drop_tablet_worker_count to half of the core number by default (backport #52246) #53124
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I'm doing:
In shared data mode, file gc relies on the efficiency of the delete file thread pool. The default thread pool size is too small, which causes the delete file task queue to accumulate easily under high ingestion concurrency or under large ingestion, resulting in slowing donw vacuum task.
What I'm doing:
In the pr, we slightly increase the delete file thread pool size into half the cpu core (
config::drop_tablet_worker_count <= 0
) If user change theconfig::drop_tablet_worker_count <= 0
at runtime, the thread pool size will also be modified as half the cpu core.Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request #52246 done by [Mergify](https://mergify.com). ## Why I'm doing: In shared data mode, file gc relies on the efficiency of the delete file thread pool. The default thread pool size is too small, which causes the delete file task queue to accumulate easily under high ingestion concurrency or under large ingestion, resulting in slowing donw vacuum task.
What I'm doing:
In the pr, we slightly increase the delete file thread pool size into half the cpu core (
config::drop_tablet_worker_count <= 0
) If user change theconfig::drop_tablet_worker_count <= 0
at runtime, the thread pool size will also be modified as half the cpu core.Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist: