-
Notifications
You must be signed in to change notification settings - Fork 243
Run Kimi K2.6 NVFP4 Dynamo vLLM on b200-new / 在 b200-new 上运行 Kimi K2.6 NVFP4 Dynamo vLLM #2438
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
RohitNagraj
wants to merge
8
commits into
main
Choose a base branch
from
kimik2.6-fp4-b200-new-runner
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
d6e0efe
chore: route Kimi K2.6 sweep to b200-new
RohitNagraj 6f0341e
chore: update perf changelog PR link
RohitNagraj 2550525
fix: configure b200-new launch environment
RohitNagraj 7eb3acb
fix: stabilize b200-new image staging
RohitNagraj 938b380
fix: use batch_1 for b200-new
RohitNagraj 57faf6d
fix: use batch_2 for b200-new
RohitNagraj fc26091
revert: restore batch_1 for b200-new
RohitNagraj 223adaf
Merge branch 'main' into kimik2.6-fp4-b200-new-runner
kedarpotdar-nv File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
112 changes: 0 additions & 112 deletions
112
...node/srt-slurm-recipes/vllm/kimi-k2.6/b200-fp4/8k1k/disagg-b200-1p1d-dep4-dep8-c1024.yaml
This file was deleted.
Oops, something went wrong.
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| #!/usr/bin/bash | ||
|
|
||
| export SLURM_PARTITION="batch_1" | ||
| export SLURM_ACCOUNT="benchmark" | ||
| export MODEL_PATH="/scratch/models/Kimi-K2.6-NVFP4" | ||
|
|
||
| export B200_SQUASH_DIR="/data/home/sa-shared/containers" | ||
| export B200_SQUASH_LOCK_TIMEOUT="3600" | ||
| mkdir -p "$B200_SQUASH_DIR" || { | ||
| echo "Unable to prepare nscale runner storage" >&2 | ||
| exit 1 | ||
| } | ||
|
|
||
| exec bash "$(dirname "${BASH_SOURCE[0]}")/launch_b200-dgxc.sh" "$@" |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 The new perf-changelog.yaml entry for
kimik2.6-fp4-b200-dynamo-vllmends with an unfilled placeholder link:pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/XXXinstead of the real PR number. Please replaceXXXwith2438to match every other entry in this append-only changelog.Extended reasoning...
The newly appended block in
perf-changelog.yaml(lines 5357-5365) documents the routing change tob200-new, but itspr-linkfield was never filled in with the actual PR number and instead ships with the literal placeholderhttps://github.com/SemiAnalysisAI/InferenceX/pull/XXX.This is verifiable directly against the committed content rather than the rendered PR diff. Running
git log --oneline -- perf-changelog.yamlshows commitd6e0efe("chore: route Kimi K2.6 sweep to b200-new") as the tip of history for this file, with a subject line that matches this PR's title exactly and — unlike the surrounding merged commits ((#2213),(#2360),(#2312)) — carries no merge-PR suffix, confirming it is this PR's own commit rather than a later, unrelated change. Bothgit show HEAD:perf-changelog.yamland the on-disk working tree confirm the last line of the new block readspr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/XXX.One verifier raised a plausible-sounding objection: the preloaded PR diff shown in review context displays
pull/2438on that line, and standard guidance says to prefer the diff over a possibly-diverged working tree. However, that guidance exists to handle the case where the checkout is ahead of the PR (later commits touched the file). That doesn't apply here — HEAD is the PR's commit, there is no later commit to discount, and the diff-displayed2438does not match what git actually recorded as committed. In other words, the "2438" appears to be a harness-level auto-substitution for display purposes, not the real content of the change. Trustinggit show/working-tree content (the actual bytes that would land in the repo) over the rendered diff is correct in this specific case, since they conflict and only one can be what actually gets merged.Step-by-step proof:
git log --oneline -- perf-changelog.yaml→ top commit isd6e0efe, no(#NNNN)suffix, subject matches this PR's title.git show HEAD:perf-changelog.yaml | tail -9→ last line of the newkimik2.6-fp4-b200-dynamo-vllmblock ispr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/XXX.tail -9 perf-changelog.yaml(working tree) → identical.../pull/XXXline, confirming it is not a stale artifact of an intermediate git state..../pull/2213, and others at.../pull/2360,.../pull/2312) has a real, resolved PR number — this is the only entry left as a placeholder.Impact is purely cosmetic:
perf-changelog.yamlis an append-only audit/documentation log, and this field is not consumed by any routing, sweep, or runtime logic — nothing breaks functionally. But it leaves a dead link (.../pull/XXX404s) in an otherwise-accurate historical record, which is a real, if minor, correctness gap. The fix is a one-line change: replaceXXXwith2438on line 5365.