Skip to content

add B300 vLLM AgentX single-node MiniMax-M3 FP4 EAGLE3-GQA MTP / 新增 B300 vLLM AgentX 单节点 MiniMax-M3 FP4 EAGLE3-GQA MTP - #2328

Open
hshrivastava-droid wants to merge 20 commits into
mainfrom
minimaxm3-fp4-b300-vllm-agentic-mtp
Open

add B300 vLLM AgentX single-node MiniMax-M3 FP4 EAGLE3-GQA MTP / 新增 B300 vLLM AgentX 单节点 MiniMax-M3 FP4 EAGLE3-GQA MTP#2328
hshrivastava-droid wants to merge 20 commits into
mainfrom
minimaxm3-fp4-b300-vllm-agentic-mtp

Conversation

@hshrivastava-droid

@hshrivastava-droid hshrivastava-droid commented Jul 24, 2026

Copy link
Copy Markdown
Collaborator

Day-zero single-node agentic-coding recipe for MiniMax-M3 (NVFP4, MoE) on B300 with vLLM and EAGLE3-GQA speculative decoding. GPU-resident KV only — no DRAM offload arm.

Contents

  • benchmarks/single_node/agentic/minimaxm3_fp4_b300_mtp.sh
  • configs/nvidia-master.yamlminimaxm3-fp4-b300-vllm-agentic-mtp (5 configs)
  • perf-changelog.yaml entry

Image: vllm/vllm-openai:nightly-387189c42997b27e2c04b5d97ef8190ffa2bf909

Draft model: Inferact/MiniMax-M3-EAGLE3-GQA — 3 speculative tokens, synthetic rejection sampling, thinking-on acceptance length 2.83 (from the canonical MiniMax-M3 EAGLE3 AL distribution, action 28061204145).

Serve flags

  • FlashInfer TRT-LLM attention (use_trtllm_attention=true) with FP8 indexer KV
  • EAGLE3 drafter on FLASH_ATTN
  • --enable-prefix-caching, --block-size 128, --gpu-memory-utilization 0.9
  • --max-cudagraph-capture-size 512, --max-num-batched-tokens 16384, --stream-interval 20
  • --reasoning-parser minimax_m3, --default-chat-template-kwargs '{"thinking_mode":"enabled"}'
  • --all2all-backend flashinfer_nvlink_one_sided

Search space

Five configs, GPU-resident KV only:

TP conc
8 1
4 1, 2, 16
2 2

dram-utilization: 0.80 is set in the matrix but only applies to DRAM-offload arms; all points here have kv-offloading: none.

Eval logic

Added EVAL_ONLY branch: when EVAL_ONLY=true the script calls run_eval --port $PORT instead of the benchmark replay path, so lm-eval can be run against a live server without re-running the full agentic sweep.


中文说明

MiniMax-M3(NVFP4,MoE)在 B300 单节点上的首日 agentic-coding 配方,使用 vLLM 搭配 EAGLE3-GQA 投机解码,仅含 GPU 驻留 KV 配置(无 DRAM 卸载分支)。

镜像:vllm/vllm-openai:nightly-387189c42997b27e2c04b5d97ef8190ffa2bf909

草稿模型:Inferact/MiniMax-M3-EAGLE3-GQA,投机 token 数 3,合成拒绝采样,thinking-on 合成接受长度 2.83(来自 MiniMax-M3 EAGLE3 AL 分布,action 28061204145)。

共 5 个配置:TP8 并发 1;TP4 并发 1、2、16;TP2 并发 2。新增 EVAL_ONLY 分支,支持对运行中的服务端单独执行 lm-eval 评估。

@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution! Please reach out to respective companies' CODEOWNER to fill in the latest PR_REVIEW_CHECKLIST.md before pinging core maintainer on Slack for review. In order for the signoff PR check bot to trigger, you must follow the PR_REVIEW_CHECKLIST.md template correctly, including the phrase As a PR reviewer and CODEOWNER, I have reviewed this and have.

For PR verification, add the full-sweep-fail-fast label (strongly recommended) to this PR — the benchmark sweep only runs on labeled PRs. Use full-sweep-enabled only if you need matrix jobs to keep running past a failure.

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. See GitHub's docs on re-running failed jobs


感谢你的贡献!请联系相应公司的 CODEOWNER 填写最新的 PR_REVIEW_CHECKLIST.md,然后再在 Slack 上联系核心维护者进行审阅。为了触发 signoff PR 检查机器人,你必须正确遵循 PR_REVIEW_CHECKLIST.md 模板,包括保留英文语句 As a PR reviewer and CODEOWNER, I have reviewed this and have

如需进行 PR 验证,请为此 PR 添加 full-sweep-fail-fast 标签(强烈推荐)— 基准测试 sweep 仅在带有标签的 PR 上运行。仅当需要矩阵任务在失败后继续运行时才使用 full-sweep-enabled

PR 作者有责任确保合并后所有 GitHub Action 任务完全通过。 很多时候失败只是偶发抖动(flake),重新运行失败的任务即可解决。参见 GitHub 关于重新运行失败任务的文档

2 similar comments
@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution! Please reach out to respective companies' CODEOWNER to fill in the latest PR_REVIEW_CHECKLIST.md before pinging core maintainer on Slack for review. In order for the signoff PR check bot to trigger, you must follow the PR_REVIEW_CHECKLIST.md template correctly, including the phrase As a PR reviewer and CODEOWNER, I have reviewed this and have.

For PR verification, add the full-sweep-fail-fast label (strongly recommended) to this PR — the benchmark sweep only runs on labeled PRs. Use full-sweep-enabled only if you need matrix jobs to keep running past a failure.

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. See GitHub's docs on re-running failed jobs


感谢你的贡献!请联系相应公司的 CODEOWNER 填写最新的 PR_REVIEW_CHECKLIST.md,然后再在 Slack 上联系核心维护者进行审阅。为了触发 signoff PR 检查机器人,你必须正确遵循 PR_REVIEW_CHECKLIST.md 模板,包括保留英文语句 As a PR reviewer and CODEOWNER, I have reviewed this and have

如需进行 PR 验证,请为此 PR 添加 full-sweep-fail-fast 标签(强烈推荐)— 基准测试 sweep 仅在带有标签的 PR 上运行。仅当需要矩阵任务在失败后继续运行时才使用 full-sweep-enabled

PR 作者有责任确保合并后所有 GitHub Action 任务完全通过。 很多时候失败只是偶发抖动(flake),重新运行失败的任务即可解决。参见 GitHub 关于重新运行失败任务的文档

@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution! Please reach out to respective companies' CODEOWNER to fill in the latest PR_REVIEW_CHECKLIST.md before pinging core maintainer on Slack for review. In order for the signoff PR check bot to trigger, you must follow the PR_REVIEW_CHECKLIST.md template correctly, including the phrase As a PR reviewer and CODEOWNER, I have reviewed this and have.

For PR verification, add the full-sweep-fail-fast label (strongly recommended) to this PR — the benchmark sweep only runs on labeled PRs. Use full-sweep-enabled only if you need matrix jobs to keep running past a failure.

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. See GitHub's docs on re-running failed jobs


感谢你的贡献!请联系相应公司的 CODEOWNER 填写最新的 PR_REVIEW_CHECKLIST.md,然后再在 Slack 上联系核心维护者进行审阅。为了触发 signoff PR 检查机器人,你必须正确遵循 PR_REVIEW_CHECKLIST.md 模板,包括保留英文语句 As a PR reviewer and CODEOWNER, I have reviewed this and have

如需进行 PR 验证,请为此 PR 添加 full-sweep-fail-fast 标签(强烈推荐)— 基准测试 sweep 仅在带有标签的 PR 上运行。仅当需要矩阵任务在失败后继续运行时才使用 full-sweep-enabled

PR 作者有责任确保合并后所有 GitHub Action 任务完全通过。 很多时候失败只是偶发抖动(flake),重新运行失败的任务即可解决。参见 GitHub 关于重新运行失败任务的文档

Comment thread benchmarks/single_node/agentic/minimaxm3_fp4_b300_mtp.sh
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@hshrivastava-droid
hshrivastava-droid force-pushed the minimaxm3-fp4-b300-vllm-agentic-mtp branch from df796e1 to a71fd2b Compare July 27, 2026 21:57
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor

@xinli-sw xinli-sw changed the title add b300 vllm agentX single-node minimaxm3 fp4 EAGLE-GQA MTP add B300 vLLM AgentX single-node MiniMax-M3 FP4 EAGLE3-GQA MTP / 新增 B300 vLLM AgentX 单节点 MiniMax-M3 FP4 EAGLE3-GQA MTP Jul 28, 2026
@github-actions

Copy link
Copy Markdown
Contributor

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor

@xinli-sw
xinli-sw force-pushed the minimaxm3-fp4-b300-vllm-agentic-mtp branch from f52ea00 to 3e84e61 Compare July 28, 2026 20:00
xinli-sw and others added 2 commits July 28, 2026 16:02
Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
… minimaxm3-fp4-b300-vllm-agentic-mtp 条目

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

@SemiAnalysisAI SemiAnalysisAI deleted a comment from xinli-sw Jul 30, 2026
@github-actions

Copy link
Copy Markdown
Contributor

2 similar comments
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

中文:将 MiniMax-M3 AgentX 扫描固定到 AIPerf PR #31,并同步当前 main。
@github-actions

Copy link
Copy Markdown
Contributor

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor

…r profiling handoff)

中文:将 MiniMax-M3 AgentX 扫描固定到 AIPerf ed05782(全局锚定性能分析切换点)

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

@xinli-sw

xinli-sw commented Aug 1, 2026

Copy link
Copy Markdown
Collaborator

/stage-results 30673796617

@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

@xinli-sw staged run 30673796617: https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-07-31~r30673796617

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

@xinli-sw 已将运行 30673796617 发布到预发布环境:https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-07-31~r30673796617

后续的 /stage-results 请求不会移除此运行;再次发布相同的运行 ID 会更新其预发布数据。预发布工作流

@xinli-sw

xinli-sw commented Aug 1, 2026

Copy link
Copy Markdown
Collaborator

/stage-results 30514549263

@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

@xinli-sw staged run 30514549263: https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-07-30~r30514549263

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

@xinli-sw 已将运行 30514549263 发布到预发布环境:https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-07-30~r30514549263

后续的 /stage-results 请求不会移除此运行;再次发布相同的运行 ID 会更新其预发布数据。预发布工作流

@xinli-sw

xinli-sw commented Aug 1, 2026

Copy link
Copy Markdown
Collaborator

/stage-results 30506325008

@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

@xinli-sw staged run 30506325008: https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-07-30~r30506325008

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

@xinli-sw 已将运行 30506325008 发布到预发布环境:https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-07-30~r30506325008

后续的 /stage-results 请求不会移除此运行;再次发布相同的运行 ID 会更新其预发布数据。预发布工作流

…hdogs active across barriers)

中文:将 MiniMax-M3 AgentX 扫描固定到 AIPerf abf55f9(跨 barrier 保持空闲看门狗活跃)

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

@xinli-sw

xinli-sw commented Aug 2, 2026

Copy link
Copy Markdown
Collaborator

/stage-results 30730035219

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

@xinli-sw staged run 30730035219: https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-08-02~r30730035219

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

@xinli-sw 已将运行 30730035219 发布到预发布环境:https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-08-02~r30730035219

后续的 /stage-results 请求不会移除此运行;再次发布相同的运行 ID 会更新其预发布数据。预发布工作流

…DRAM arms

TP4 GPU-resident: [1,2,5,10,15,20]; TP2 GPU-resident: [1,2,5,10,15,20]; TP4 DRAM offload: [20,30,40,50,60]

中文:扩展 MiniMax-M3 B300 MTP AgentX 扫描空间:TP4 GPU 驻留 [1,2,5,10,15,20];TP2 GPU 驻留 [1,2,5,10,15,20];TP4 DRAM 卸载 [20,30,40,50,60]

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

@xinli-sw

xinli-sw commented Aug 2, 2026

Copy link
Copy Markdown
Collaborator

/stage-results 30733110281

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

@xinli-sw staged run 30733110281: https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-08-02~r30733110281

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

@xinli-sw 已将运行 30733110281 发布到预发布环境:https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-08-02~r30733110281

后续的 /stage-results 请求不会移除此运行;再次发布相同的运行 ID 会更新其预发布数据。预发布工作流

…offload

TP2: [1,2,5] (drop c10,c15,c20); TP4 DRAM: [30,40,50,60,80,90,100] (drop c20, add c80/90/100)

中文:精简扫描空间——TP2 缩减至 [1,2,5],TP4 DRAM 卸载调整为 [30,40,50,60,80,90,100]

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

@xinli-sw

xinli-sw commented Aug 2, 2026

Copy link
Copy Markdown
Collaborator

/stage-results 30751989616

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

@xinli-sw staged run 30751989616: https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-08-02~r30751989616

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

@xinli-sw 已将运行 30751989616 发布到预发布环境:https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-08-02~r30751989616

后续的 /stage-results 请求不会移除此运行;再次发布相同的运行 ID 会更新其预发布数据。预发布工作流

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

6 participants