Enable NUMA-aware scheduling for H100 4-GPU runner (#696)#737
Draft
georgehong wants to merge 1 commit into
Draft
Enable NUMA-aware scheduling for H100 4-GPU runner (#696)#737georgehong wants to merge 1 commit into
georgehong wants to merge 1 commit into
Conversation
tofu plan — arc-cbr-production✅ Plan succeeded · commit Plan output |
tofu plan — arc-cbr-production-uw1✅ Plan succeeded · commit Plan output |
tofu plan — meta-prod-aws-ue1✅ Plan succeeded · commit Plan output |
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
1 participant
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.
Stack from ghstack (oldest at bottom):
Adds per-runner-def scheduler_name support to generate_runners.py
and sets scheduler_name: numa-scheduler on the H100 4-GPU runner
(l-x86iamx-88-900-h100-4). Workflow pods for this runner will use
the numa-scheduler deployed in the previous commit, which checks
NRT data to ensure a single NUMA zone can satisfy the full 4-GPU
request before placing the pod — preventing TopologyAffinityError
on fragmented p5.48xlarge nodes.
Other runners are unaffected (no scheduler_name in their defs =
default scheduler).
Part of #696