Add representative MoE timing experiment runners#96
Draft
Happymic wants to merge 1 commit into
Draft
Conversation
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.
What This PR Does
This PR adds the P3 orchestration layer for representative MoE timing runs. It organizes the longer-running experiment drivers separately from the P2 pilot trace replay code.
Concrete Changes
window1_p3/run_p3_rev_subset.pyfor representative subset runs.window1_p3/run_p3_scale_batch.pyfor scale/batch sweeps.window1_p3/wait_p3_rev_stage_b.pyto wait for and summarize Stage-B progress.window1_p3/watch_p3_rev_raw_build.pyto watch raw-build progress.window1_p3package instead of mixing them intowindow1_p2.window1_p2.run_p3_*self-references and local hardcoded cwd defaults.What This PR Does Not Do
Validation
Ran locally:
After rebasing onto the portable P2 branch: