graph_trainer: add named EP overlap schedules - #4022
Closed
sanketpurandare wants to merge 1 commit into
Closed
Conversation
## Summary Add an explicit named-schedule mode alongside the dependency-driven auto scheduler. Schedules use typed token-exchange, module-FQN, and ready-filler anchors, and the DeepSeek-v3 policy represents the calibrated forward, saved-backward, and full-recompute ordering. Token anchors schedule only the dependency closure needed to launch an exchange. Every exchange must be covered exactly, and malformed or dependency-invalid schedules fail with region context. ## Why Named schedules make communication/compute placement reproducible and allow model-aware alternatives to greedy filling without adding model-specific branches to the generic scheduler. ## Test Plan - Validate unknown schedule names and DeepSeek-v3 provider applicability. - Run an exact two-rank DeepSeek-v3 comparison between named and auto graph schedules. - Compare both loss and gradient norm for 20 steps with full recomputation, forced-balanced routing, and regional Inductor. [ghstack-poisoned]
This was referenced Jul 28, 2026
This was referenced Jul 29, 2026
Contributor
Author
|
Closing this experimental named-schedule direction and removing it from the landing stack. The retained stack uses the shared automatic scheduler and bounded MinimalAsyncEP copies. |
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.
Stack from ghstack (oldest at bottom):
Summary
Add an explicit named-schedule mode alongside the dependency-driven auto
scheduler. Schedules use typed token-exchange, module-FQN, and ready-filler
anchors, and the DeepSeek-v3 policy represents the calibrated forward,
saved-backward, and full-recompute ordering.
Token anchors schedule only the dependency closure needed to launch an
exchange. Every exchange must be covered exactly, and malformed or
dependency-invalid schedules fail with region context.
Why
Named schedules make communication/compute placement reproducible and allow
model-aware alternatives to greedy filling without adding model-specific
branches to the generic scheduler.
Test Plan
schedules.
forced-balanced routing, and regional Inductor.