Raise runner prepare defaults#601
Merged
pan-x-c merged 1 commit intoJul 7, 2026
Merged
Conversation
Collaborator
|
/unittest-module-explorer |
unittest: Run #1812
❌ Some tests failed!
Github Test Reporter by CTRF 💚 |
Collaborator
|
/unittest-pattern-TestExplorerGSM8KRULERNoEval |
unittest: Run #1813
🎉 All tests passed!Github Test Reporter by CTRF 💚 |
pan-x-c
approved these changes
Jul 7, 2026
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.
Summary
runner_prepare_concurrencyfrom 8 to 128.runner_prepare_max_retriesfrom 2 to 3.Motivation
The current default concurrency of 8 can slow down large workflow-runner cold starts. In DLC profiling, each runner prepare can take around 70 seconds, so preparing many runners in batches of 8 can noticeably delay startup and GPU utilization.
The 128 value keeps a conservative default guardrail for mass startup. If maintainers prefer simpler behavior, keeping only the retry mechanism may also be enough, since transient runner-prepare failures are already retried.
Checks
python -m py_compile trinity/common/config.py