Fix ramp-up worker scaling - #27
Merged
Merged
Conversation
|
I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Motivation
get_all_responsesruns.Description
worker_spawnerloop and a helper_desired_worker_count()to gradually spawn new worker tasks as the ramp increases the parallel cap inget_all_responses(filesrc/gabriel/utils/openai_utils.py)._maybe_emit_ramp_complete()so ramp completion is emitted even when the periodicstatus_reporteris disabled.workerslist and start an initial set of workers via_desired_worker_count()instead of creating a static pool upfront.Testing
pytest tests/test_parallelization_tuning.py::test_ramp_up_increases_parallelism, which passed.Codex Task