-
Notifications
You must be signed in to change notification settings - Fork 243
[NV] minimax-m3-b200/b300-mtp: update fp8 MTP to vLLM nightly / [NV] minimax-m3-b200/b300-mtp:将 FP8 MTP 更新至 vLLM nightly #2337
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
Merged
+24
−86
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
7148fb9
[NV] minimax-m3-b200/b300-mtp: vLLM nightly image, GQA draft head, FL…
xinli-sw 1274cd2
[NV] minimax-m3-b200/b300-mtp: add perf-changelog pr-link
xinli-sw 924e327
Merge remote-tracking branch 'origin/main' into minimaxm3-fp8-b200-b3…
xinli-sw 315b9a0
[NV] minimax-m3-b200/b300-mtp: drop tp4-ep4-DEP (dp-attn) arm from th…
xinli-sw 6ba556e
Merge remote-tracking branch 'origin/main' into pr-2337-reuse-50331
Ankur-singh 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
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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 config comments above minimaxm3-fp8-b200-vllm-mtp (~line 7458-7459) and minimaxm3-fp8-b300-vllm-mtp (~line 7513) still say the drafter is 'Inferact/MiniMax-M3-EAGLE3' pinned to 'TRITON_ATTN', but this PR switches both recipes to 'Inferact/MiniMax-M3-EAGLE3-GQA' with 'FLASH_ATTN'. Please update these two comment blocks to match, similar to how the h200/h100 mtp entries already describe the FLASH_ATTN/GQA rationale.
Extended reasoning...
configs/nvidia-master.yamlcontains a hand-written comment block directly above eachminimaxm3-fp8-*-vllm-mtpconfig entry explaining the EAGLE3 speculative-decoding setup for that recipe. Forminimaxm3-fp8-b200-vllm-mtpthe comment (around lines 7456-7459) reads: "...adds the Inferact/MiniMax-M3-EAGLE3 draft head... The target uses the FlashInfer TRT-LLM attention path. The EAGLE3 drafter is pinned separately to TRITON_ATTN." Forminimaxm3-fp8-b300-vllm-mtpthe comment (around lines 7511-7513) similarly references the plainInferact/MiniMax-M3-EAGLE3draft head with no attention-backend caveat.This PR changes exactly what those comments describe: the draft head becomes
Inferact/MiniMax-M3-EAGLE3-GQAand the speculativeattention_backendmoves fromTRITON_ATTNtoFLASH_ATTN(visible in the matching.shrecipe diffs, where the header comments were correctly updated: "Inferact/MiniMax-M3-EAGLE3-GQA draft head" and "The EAGLE3-GQA drafter is pinned separately to FLASH_ATTN."). However, the diff hunk touchingconfigs/nvidia-master.yamlonly replaces theimage:line inside each block (lines 7461-7467 for b200, 7517-7523 for b300) — the descriptive comment lines sitting just above those keys were left untouched.The result is that after this PR merges, the YAML comments for the b200 and b300 mtp entries misdescribe the actual recipe: they name the wrong draft-head repo (missing "-GQA") and, for b200, explicitly claim the drafter is "pinned to TRITON_ATTN" when it is now pinned to FLASH_ATTN. This is a real inconsistency the PR introduces/worsens, not a pre-existing one, since the PR's own script changes are what make the comments wrong. Contrast this with the sibling h200/h100 mtp entries further down in the same file (~lines 7539-7546 and 7565-7570), which already correctly explain the FLASH_ATTN/GQA rationale — those are the template this PR's two comment blocks should be brought in line with.
Step-by-step proof: (1) Before this PR, b200 mtp comment says draft head =
Inferact/MiniMax-M3-EAGLE3, backend =TRITON_ATTN, matching the old script'sDRAFT_MODEL="Inferact/MiniMax-M3-EAGLE3"and"attention_backend": "TRITON_ATTN". (2) This PR's diff tominimaxm3_fp8_b200_mtp.shchangesDRAFT_MODELto"Inferact/MiniMax-M3-EAGLE3-GQA"andattention_backendto"FLASH_ATTN", and updates that script's own header comment to match. (3) Theconfigs/nvidia-master.yamldiff for the same recipe only touches theimage:line — the comment block above it is byte-for-byte identical to before. (4) Therefore post-merge, the YAML comment and the actual recipe behavior diverge: reading the config comment alone, a maintainer would believe the drafter still uses TRITON_ATTN with the non-GQA head, which is now false. The same divergence applies to the b300 comment (missing "-GQA" and no FLASH_ATTN mention).This is comment-only and has zero effect on runtime behavior — the scripts themselves (the actual source of truth for how the benchmark runs) are correct. So while it's a genuine, PR-introduced inconsistency worth fixing to keep the config self-documenting, it doesn't block anything at merge. Fix: update the two comment blocks in
configs/nvidia-master.yamlto say "Inferact/MiniMax-M3-EAGLE3-GQA draft head" and "pinned separately to FLASH_ATTN" (b200) / add the same GQA/FLASH_ATTN mention (b300), mirroring the phrasing already used in the h200/h100 mtp comments.