Map overlap GPUs through infer placement#19
Open
TianyeGGBond wants to merge 1 commit into
Open
Conversation
ea4cdc2 to
541844b
Compare
541844b to
32a5485
Compare
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.
Context
_wait_for_overlap_engines_offloadedreceives physical GPU IDs from the scheduler, while the rollout manager expects local engine indices within the pipeline's inference placement. The previous conversion assumed the inference GPUs were contiguous and derived engine indices by subtracting the first GPU ID.Change
_resolve_overlap_infer_enginesunder the file's Helpers sectionactor_inferplacementoverlap_engine_indicesandoverlap_gpu_idsfor the wait logicrollout_num_gpus_per_engineValidation
python -m py_compile rlix/pipeline/miles_pipeline.pygit diff --check