[Store] Structure FilereadWorkerPoolConfig environment settings - #4166
Merged
Aionw merged 1 commit intoSep 17, 2026
Merged
Conversation
Signed-off-by: Schatten <czhengt@qq.com>
bitborne
requested review from
XucSh,
YiXR,
stmatengss and
ykwd
as code owners
September 16, 2026 15:49
Aionw
approved these changes
Sep 17, 2026
ykwd
approved these changes
Sep 17, 2026
This was referenced Sep 17, 2026
13 tasks
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
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.
Description
Part of #3809. Extract
MC_FILEREAD_WORKERSfrom the transfer-task source into a private, client-ownedFilereadWorkerPoolConfigand the common environment catalog. The worker pool still takes one process-wide snapshot on first construction, defaults to 10 workers for absent/empty/invalid values, and emits the existing warning with the raw input for a nonempty invalid value. The unrelated NoF settings and the public worker-pool API stay unchanged.The shared typed integer parser is used for nonempty input. This intentionally accepts surrounding ASCII whitespace (for example,
"2 "), which the previousstrtolpath rejected; the supported positive integer behavior and first-use caching are covered by direct config and worker-count tests. This is a single-owner extraction following merged PRs #3872 and #4036.Open PR #3424 also edits
transfer_task.cppwhile refactoring NoF internals, including the adjacent#ifdef USE_NOFboundary. It does not migrateMC_FILEREAD_WORKERS; if it merges before this PR, the NoF guard overlap needs resolving at integration time. This PR does not rebase or modify NoF behavior preemptively.Module
mooncake-store)mooncake-common)Type of Change
How Has This Been Tested?
Test commands:
Test results:
The unfiltered target has one pre-existing GPU pinned-host allocation failure:
TransferTaskTest.BatchGetOffloadObjectCopiesPinnedHostToGpugets a null buffer. The same test fails at the same assertion in the independently built branch with unmodified fileread worker code, and fails when run alone; it is not caused by this extraction. Before the production change, the new whitespace/worker-count test failed against the old parser; after the change its isolated binary passes 10 repetitions. The client object target builds, and touched-file pre-commit and staged-line clang-format 20 checks pass.Checklist
./scripts/code_format.shNo documentation update: the public API and positive-integer contract remain the same; whitespace acceptance is described above.
AI Assistance Disclosure
Codex assisted with ownership analysis, implementation, RED-to-GREEN focused tests, build/format/hook verification, and review. The human submitter will review every changed line and is responsible for the change end to end.