feat(loader): cap default insert workers to min(cpu, 4)#767
Merged
XuanYang-cn merged 1 commit intozilliztech:mainfrom Apr 24, 2026
Merged
feat(loader): cap default insert workers to min(cpu, 4)#767XuanYang-cn merged 1 commit intozilliztech:mainfrom
XuanYang-cn merged 1 commit intozilliztech:mainfrom
Conversation
ConcurrentInsertRunner previously defaulted to mp.cpu_count(), spawning one worker per CPU when load_concurrency was unset. On high-core hosts this opens many parallel client connections, saturating modest DBs / network paths and yielding worse load throughput than a smaller, steadier worker count. Cap the unset default to min(cpu_count, 4). Explicit load_concurrency from CLI / config / submitTask still wins. Signed-off-by: yangxuan <xuan.yang@zilliz.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: XuanYang-cn The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
ConcurrentInsertRunner previously defaulted to mp.cpu_count(),
spawning one worker per CPU when load_concurrency was unset.
On high-core hosts this opens many parallel client connections,
saturating modest DBs / network paths and yielding worse
load throughput than a smaller, steadier worker count.
Cap the unset default to min(cpu_count, 4). Explicit
load_concurrency from CLI / config / submitTask still wins.