Skip to content

[Klaud Cold] minimaxm31flash-fp4-h100-vllm-agentic-dspark: day-zero MiniMax-M3.1-Flash H100 DSpark recipe - #4422

Merged
Oseltamivir merged 7 commits into
mainfrom
feat/minimaxm31flash-h100-h200-dayzero
Oct 23, 2026
Merged

Oseltamivir merged 7 commits into
mainfrom
feat/minimaxm31flash-h100-h200-dayzero

Conversation

@Oseltamivir

@Oseltamivir Oseltamivir commented Oct 23, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Day-zero MiniMax-M3.1-Flash DSpark (MiniMaxAI/MiniMax-M3.1-Flash) AgentX on H100 with vLLM, from https://vllm.ai/blog/2026-10-23-minimax-m31-flash. This follows the Hopper section of https://recipes.vllm.ai/MiniMaxAI/MiniMax-M3.1-Flash.

  • Image: vllm/vllm-openai:minimax-m31-flash, pinned to the multiarch digest sha256:86f582da… (amd64 = minimax-m31-flash-x86_64-cu134). This is the same pin as the B200/B300 PR.
  • Serve flags: TP8, --block-size 128, --kv-cache-dtype fp8, indexer_kv_dtype: fp8, --moe-backend marlin (NVFP4 experts; Hopper has no FP4 tensor cores), FULL_AND_PIECEWISE graphs, --disable-hybrid-kv-cache-manager, and the minimax_m3 reasoning and tool parsers.
  • Deviation from upstream: max-model-len is 1M rather than the 256K in the upstream Hopper example. The AgentX corpus for this prefix is uncapped, and the Blackwell arms also run at 1M.
  • Speculative decoding: three-token DSpark, using the GB200 recipe's config (FLASH_ATTN drafter, fp8 draft KV, block rejection). Upstream doesn't enable DSpark on Hopper, so whether the drafter runs on Hopper is still unverified. Throughput runs use synthetic acceptance from minimaxm31flash_dspark.yaml, which isn't committed yet (an AL curve run is in progress). The sweep is on hold until it lands.
  • Search space: TP8, conc 1–12 (h100-dsxe), no KV offload. Scaled from the MiniMax-M3 H100 HBM cliff (c5–c6), using the smaller 250 GB checkpoint.

Siblings: #4423 (H200), #4419 (GB200/GB300), #4420 (MI355X), #4421 (B200/B300).

🤖 Generated with Claude Code

…ash AgentX on H100/H200

Hopper TP8 recipe from recipes.vllm.ai: FP8 KV and indexer caches, NVFP4
experts on Marlin MoE, block size 128, FULL_AND_PIECEWISE graphs. No DSpark
on Hopper upstream. Context kept at 1M for the uncapped AgentX corpus.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution!

  • Review: If this PR changes files owned by someone other than a repository admin or @SemiAnalysisAI/core, ask one eligible CODEOWNER to complete the latest PR_REVIEW_CHECKLIST.md before contacting a core maintainer on Slack. Follow the template exactly, including As a PR reviewer and CODEOWNER, I have reviewed this and have, so sign-off verification triggers.
  • PR verification: Sweeps run only when the PR appends an inferencex-e2e/perf-changelog.yaml entry and carries exactly one primary label: full-sweep-fail-fast (strongly recommended; canary plus per-matrix fail-fast), full-sweep-enabled (canary; matrix jobs continue after a failure), or non-canary-full-sweep-enabled (no canary or fail-fast). The modifiers all-evals, evals-only, and agentx-fast require a primary label. On fork PRs, a maintainer applies the label. See sweep labels and reuse.
  • After merging: PR authors must ensure all GitHub Actions jobs pass. Transient failures often pass on rerun; see how to rerun failed jobs.
中文

感谢你的贡献!

  • **审阅:**如果 PR 修改的文件归属于仓库管理员及 @SemiAnalysisAI/core 之外的 CODEOWNER,请先联系一位有资格的 CODEOWNER 填写最新的 PR_REVIEW_CHECKLIST.md,再通过 Slack 联系核心维护者。必须严格遵循模板,并保留 As a PR reviewer and CODEOWNER, I have reviewed this and have,才能触发签核验证。
  • **PR 验证:**只有当 PR 在 inferencex-e2e/perf-changelog.yaml 末尾追加了条目,并且恰好带有一个主标签时,才会运行扫描:full-sweep-fail-fast(强烈推荐;canary 加逐矩阵 fail-fast)、full-sweep-enabled(有 canary;矩阵任务在失败后继续运行)或 non-canary-full-sweep-enabled(无 canary,也无 fail-fast)。修饰标签 all-evals、evals-only 和 agentx-fast 必须与主标签一起使用。fork PR 的标签由维护者添加。参见扫描标签与复用。
  • **合并后:**PR 作者必须确保所有 GitHub Actions 任务通过。临时性失败通常可以通过重新运行恢复;参见重新运行失败任务的说明。

@Oseltamivir Oseltamivir added the full-sweep-fail-fast Full sweep with canary gate; first failure cancels the rest of that matrix (recommended) label Oct 23, 2026
…n DSpark

Use the GB200 recipe's DSpark config (FLASH_ATTN drafter, fp8 draft KV,
block rejection) and scale graph capture to four tokens per sequence.
Throughput runs need the minimaxm31flash_dspark golden curve.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Oseltamivir Oseltamivir removed the full-sweep-fail-fast Full sweep with canary gate; first failure cancels the rest of that matrix (recommended) label Oct 23, 2026
@Oseltamivir Oseltamivir changed the title [Klaud Cold] minimaxm31flash-fp4-h{100,200}-vllm-agentic: day-zero MiniMax-M3.1-Flash H100/H200 recipe [Klaud Cold] minimaxm31flash-fp4-h{100,200}-vllm-agentic-dspark: day-zero MiniMax-M3.1-Flash H100/H200 DSpark recipe Oct 23, 2026
@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Findings marked 🟡 are optional suggestions and need no follow-up push.

Comment thread inferencex-e2e/perf-changelog.yaml Outdated
- "Add day-zero MiniMax-M3.1-Flash (MiniMaxAI/MiniMax-M3.1-Flash, NVFP4 experts + MXFP8 dense) AgentX on H100 and H200 with vLLM image minimax-m31-flash (https://vllm.ai/blog/2026-10-23-minimax-m31-flash)."
- "Serve flags follow the recipes.vllm.ai Hopper TP8 recipe: block size 128, FP8 KV and indexer cache, Marlin MoE backend for the NVFP4 experts, FULL_AND_PIECEWISE graphs, hybrid KV cache manager disabled, minimax_m3 reasoning and tool parsers. Context stays at 1M (upstream Hopper example uses 256K) because the AgentX corpus for this prefix is uncapped."
- "Search space: TP8 only, H100 conc 1-12 and H200 conc 1-24, no KV offloading. Upstream does not enable DSpark on Hopper."
pr-link: TBD

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 The changelog validator will reject this PR's new entry. pr-link: TBD is neither the PR URL nor an accepted placeholder. Neither config would get a valid changelog record. validate_added_pr_link accepts only XXX, https://github.com/SemiAnalysisAI/InferenceX/pull/XXX, or the canonical PR URL. Merge-time canonicalization also rewrites only those placeholders. Fix: set pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/XXX (or the real PR number), as CONTRIBUTING.md shows.

Why this was flagged

The new entry appended at inferencex-e2e/perf-changelog.yaml:10882 has pr-link: TBD. On a PR run, validate_added_pr_link in inferencex-e2e/infx/workflows/validate_perf_changelog.py:139-150 raises ChangelogValidationError "new PR entry must use '.../pull/' or an XXX placeholder; found 'TBD'", because PR_LINK_PLACEHOLDERS (lines 22-25) holds only "XXX" and the pull/XXX URL. On a main-branch run it fails CANONICAL_PR_LINK.fullmatch with "new main-branch entry has invalid pr-link". The changelog check therefore fails for this PR. It is the only TBD pr-link in the file, and every other placeholder entry uses pull/XXX.

Verification: The appended entry at inferencex-e2e/perf-changelog.yaml:10882 still says pr-link: TBD. validate_added_pr_link (inferencex-e2e/infx/workflows/validate_perf_changelog.py:139-150) raises on it. Merge-time canonicalization fails, so the entry cannot be rewritten to the canonical link. The PR-run CI check does not raise this.

Comment on lines +25 to +28
# Serve flags follow the Hopper TP8 recipe at
# https://recipes.vllm.ai/MiniMaxAI/MiniMax-M3.1-Flash. Hopper has no FP4
# tensor cores, so the KV and indexer caches are FP8 and the NVFP4 experts
# run on Marlin. Upstream does not enable DSpark on Hopper.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 nit (optional): The new recipes carry history and derivation comments, which AGENTS.md:64-66 forbids. sweep:follow the Hopper TP8 recipe|as on the MiniMax-M3 H100 arm|like the Blackwell arms|Upstream does not enable DSpark Example: h100-fp4/agentic.yaml:25-28 says where the flags came from. Fix: keep only the technical reason for each line, e.g. "Hopper has no FP4 tensor cores, so the NVFP4 experts run on Marlin". This is separate from the master-config comment finding, which does not touch the recipe files. [also at: inferencex-e2e/configs/nvidia-master.yaml:5278 - Maintainers get header and provenance comments that AGENTS.md's mandatory "Code comments" rules forbid (no header comments, no history).]

Why this was flagged

AGENTS.md:65 says comments must not say where code was derived from. AGENTS.md:64 bans comments above a recipe or section. The new recipes add "Serve flags follow the Hopper TP8 recipe at https://recipes.vllm.ai/..." at h100-fp4/agentic.yaml:25-28 and h200-fp4/agentic.yaml:25-28. They add "as on the MiniMax-M3 H100 arm" at h100-fp4/agentic.yaml:51 and "like the Blackwell arms" at line 45 of both recipes. The already-filed comment finding is anchored in nvidia-master.yaml, so fixing it leaves these recipe comments in place.

Verification: AGENTS.md "Code comments (mandatory)" applies "to every file, including recipes, configs". It says "No history. Do not write comments that describe ... where it was derived from". h100-fp4/agentic.yaml lines 25-28 and h200-fp4/agentic.yaml lines 25-28 contain "# Serve flags follow the Hopper TP8 recipe", which is a derivation comment. Nothing breaks at runtime.

# 2026-10-23 (amd64 is minimax-m31-flash-x86_64-cu134). Serve flags follow the
# Hopper TP8 recipe: FP8 KV and indexer caches, NVFP4 experts on Marlin MoE.
# Upstream does not enable DSpark on Hopper.
minimaxm31flash-fp4-h100-vllm-agentic:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 (optional) Operators who run full-sweep --model-prefix minimaxm3, such as the EVALS.md MiniMax-M3 smoke runbook, will now also get MiniMax-M3.1-Flash H100/H200 jobs. The filter at generate.py:1169 uses key.startswith(p), and minimaxm31flash-… keys start with minimaxm3. Fix: match only the whole prefix (key == p or key.startswith(f"{p}-"), the rule ci_priority.py:43 already uses), so minimaxm3 stops selecting minimaxm31flash. The same change stops dsv4 from selecting dsv41flash, which already happens on the base branch.

Why this was flagged

expand_full_sweep at inferencex-e2e/infx/matrix/generate.py:1169 keeps a master config when any(key.startswith(p) for p in options.model_prefix). This PR adds the keys minimaxm31flash-fp4-h100-vllm-agentic (nvidia-master.yaml:5279) and minimaxm31flash-fp4-h200-vllm-agentic (:5301). They are the first keys whose name starts with minimaxm3 without being MiniMax-M3. inferencex-e2e/infx/evals/EVALS.md:100-106 documents full-sweep ... --model-prefix minimaxm3 as the command that builds the MiniMax-M3 deployment-smoke matrix. On the base branch that command matches only minimaxm3 configs. After merge it also emits the 7 H100 and 8 H200 Flash points. Those take whole 8-GPU h100-dsxe and h200-dgxc nodes and mix a different model into the MiniMax-M3 smoke results. Nothing guards against this, because the --model-prefix help text at generate.py:1600 promises a model-prefix filter but the code compares config-key prefixes.

Verification: Trigger: an operator runs full-sweep --model-prefix minimaxm3, the documented smoke command in inferencex-e2e/infx/evals/EVALS.md:101-106. inferencex-e2e/infx/matrix/generate.py:1169 keeps a config when any(key.startswith(p) for p in options.model_prefix), with no delimiter. At the base commit every matching key is minimaxm3-.... At HEAD the two new minimaxm31flash-... keys (nvidia-master.yaml:5279, :5301) also match.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Oseltamivir Oseltamivir changed the title [Klaud Cold] minimaxm31flash-fp4-h{100,200}-vllm-agentic-dspark: day-zero MiniMax-M3.1-Flash H100/H200 DSpark recipe [Klaud Cold] minimaxm31flash-fp4-h100-vllm-agentic-dspark: day-zero MiniMax-M3.1-Flash H100 DSpark recipe Oct 23, 2026
Oseltamivir and others added 2 commits October 23, 2026 13:02
@Oseltamivir Oseltamivir added the full-sweep-fail-fast Full sweep with canary gate; first failure cancels the rest of that matrix (recommended) label Oct 23, 2026
@Oseltamivir

Copy link
Copy Markdown
Collaborator Author

/use 39903571329

@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

@Oseltamivir staged run 39903571329.

This run remains available across future /stage-results requests. Staging the same run ID again updates its staged data. Staging workflow

@Oseltamivir
Oseltamivir merged commit 1d887cb into main Oct 23, 2026
26 checks passed
@Oseltamivir
Oseltamivir deleted the feat/minimaxm31flash-h100-h200-dayzero branch October 23, 2026 10:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

full-sweep-fail-fast Full sweep with canary gate; first failure cancels the rest of that matrix (recommended)

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant