Repository navigation
[Klaud Cold] minimaxm31flash-fp4-b300-sglang-agentic-dspark: day-zero MiniMax-M3.1-Flash B300 SGLang recipe - #4441
Conversation
…-Flash SGLang AgentX on B300 Serve flags follow the SGLang cookbook's MiniMax-M3.1 cells with the day-zero dev-minimax-m31-flash image. Seven-token DSpark with synthetic acceptance from the minimaxm31flash_dspark golden curve.
|
Thanks for the contribution!
中文感谢你的贡献!
|
| - "Serve flags follow the cookbook's B300 Balanced (TP4) and High-Throughput (TP8, attention DP2, EP8): DSpark with block verification, breakable prefill graphs, minimax-m3 reasoning and tool parsers, 8 tokenizer workers." | ||
| - "Seven-token DSpark (the bundled draft's dspark_block_size); throughput runs use synthetic acceptance from the minimaxm31flash_dspark golden curve (AL 4.04 at 7 draft tokens, #4425)." | ||
| - "Search space: Balanced TP4 at conc 1-32; TP8 + EP8 with attention DP2 at conc 64-256." | ||
| pr-link: TBD |
There was a problem hiding this comment.
🔴 The changelog check will reject this PR because its new entry's pr-link: TBD is not an accepted placeholder. Merge-time canonicalization will also skip it. validate_added_pr_link (infx/workflows/validate_perf_changelog.py:147) only accepts XXX, https://github.com/SemiAnalysisAI/InferenceX/pull/XXX, or the PR's own URL. Fix: change the line to pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/XXX or to the real PR URL. Every other appended entry in the file uses one of those forms.
Why this was flagged
The PR appends an entry whose pr-link is TBD (inferencex-e2e/perf-changelog.yaml:11018). On PR runs, validate_added_pr_link (inferencex-e2e/infx/workflows/validate_perf_changelog.py:139-150) accepts only PR_LINK_PLACEHOLDERS = {"XXX", "https://github.com/SemiAnalysisAI/InferenceX/pull/XXX"} or the expected PR URL. Anything else raises new PR entry must use ... or an XXX placeholder; found 'TBD'. On main-branch runs it must fully match CANONICAL_PR_LINK, so TBD raises new main-branch entry has invalid pr-link. The changelog validation fails, which blocks the sweep and merge. The merge-time placeholder rewrite in prepare_perf_changelog_merge.py / merge_with_reuse.py only targets the XXX placeholders, so it will not fix TBD either. No earlier entry in the file uses TBD; the other placeholders are .../pull/XXX (e.g. lines 10697, 10813).
Verification: The new entry sets pr-link: TBD (inferencex-e2e/perf-changelog.yaml:11018). merge_with_reuse.py:631 calls canonicalize_changelog(pr, repo). At validate_perf_changelog.py:147, validate_added_pr_link raises new PR entry must use ... or an XXX placeholder; found 'TBD'. canonicalize_changelog has no try/except, so the merge aborts.
| # MiniMax-M3.1-Flash AgentX on B300 with SGLang: day-zero image from the SGLang | ||
| # cookbook (https://docs.sglang.io/cookbook/autoregressive/MiniMax/MiniMax-M3.1), | ||
| # manifest digest verified 2026-10-24. Serve flags follow the cookbook's | ||
| # B300 Balanced (TP4) and High-Throughput (TP8, attention DP2, EP8). | ||
| # Seven-token DSpark (bundled draft); synthetic acceptance follows | ||
| # infx/golden_al_distribution/minimaxm31flash_dspark.yaml. |
There was a problem hiding this comment.
🟡 nit (optional): The new config and recipe add header and provenance comments, which the mandatory comment rules in AGENTS.md:64-65 forbid. sweep:^# (MiniMax-M3.1-Flash AgentX|TP4 Balanced cell|High-Throughput cell)|# Serve flags follow the cookbook For example, nvidia-master.yaml:9362-9367 describes the config and says "manifest digest verified 2026-10-24". It is also dated a day after the PR was opened. Fix: delete these block, section and provenance comments. Keep only short per-line technical reasons, such as the dp-attn note. The cookbook URL and verification details already live in the perf-changelog entry.
Why this was flagged
AGENTS.md:62-66 says the comment rules cover every file, recipes and configs included. It bans comments above a recipe, override or section, and comments that describe the config. It also bans comments saying where something came from. The diff adds a 6-line block above minimaxm31flash-fp4-b300-sglang-agentic-dspark (nvidia-master.yaml:9362-9367) that describes the topology and records provenance ("day-zero image from the SGLang cookbook", "manifest digest verified 2026-10-24"). The recipe adds section comments above the override groups (agentic.yaml:51-52 and 129-131) and a cookbook-source comment (agentic.yaml:24-25). Reviewers and the CODEOWNER checklist have to flag these, and the comments are new rule violations that the base does not have. The verification date in the master config is after the PR's open date (2026-10-23), so that provenance claim is also unreliable.
Verification: nit: this happens on every merge of these files as written. AGENTS.md "Code comments (mandatory)" says "No header comments" and "No history". The diff adds a 6-line block right above minimaxm31flash-fp4-b300-sglang-agentic-dspark: in nvidia-master.yaml that describes the config and its provenance. The recipe adds the same kind of comments. Nothing breaks at runtime.
Keep main's entries and re-add the B300 SGLang changelog and master-config blocks.
|
View unofficial run (performance): https://inferencex.semianalysis.com/inference?unofficialRun=40065872492 View unofficial run (accuracy): https://inferencex.semianalysis.com/evaluation?unofficialRun=40065872492 |
|
/use 40065872492 |
|
@Oseltamivir staged run 40065872492. This run remains available across future |
|
Ingest report — ✅ Results ingested into the Ingest workflow · Merge Ingest run · Benchmark source run
benchmarkFiles 9, rawBenchmarkRows 16, coveredByPerJobFiles 8, purgedPoints 0, failedRunRows 0, runStatsNew 0, runStatsDuplicate 0, evalSamplesNew 1319, gpuMetricSamplesNew 274092, powerPublicationPoints 8, changelogEntriesWritten 1 Counts cover only this run. Rows: benchmark_results, eval_results, agentic rows linked to a trace, gpu_metrics series. This comment updates if the ingest is rerun. 中文Ingest 报告 — ✅ 结果已写入 上表仅统计本次运行写入的数据,各行单位依次为 benchmark_results 行、eval_results 行、已关联 trace 的 agentic 行和 gpu_metrics 序列。重新运行 ingest 时本评论会原地更新。 |
Summary
Day-zero MiniMax-M3.1-Flash (
MiniMaxAI/MiniMax-M3.1-Flash, NVFP4) AgentX on B300 with SGLang, following the SGLang cookbook: https://docs.sglang.io/cookbook/autoregressive/MiniMax/MiniMax-M3.1 (config source:docs/src/snippets/configs/MiniMaxAI/minimax-m3.1.jsx).lmsysorg/sglang:dev-minimax-m31-flash, pinned by digest (verified on Docker Hub 2026-10-24).--attn-dp-size 2, EP8 MegaMoE) for conc 64–256. The matrix row istp: 8, ep: 8with dp-attn false, because the matrix's dp-attn means full DP attention.--speculative-algorithm DSPARK --speculative-use-block-verification,--cuda-graph-backend-prefill breakable,minimax-m3reasoning and tool parsers,--tokenizer-worker-num 8.--speculative-dspark-block-size 7, the bundled draft'sdspark_block_size). It's set explicitly so throughput runs resolve synthetic acceptance fromminimaxm31flash_dspark.yaml([Klaud Cold] Add MiniMax-M3.1-Flash DSpark golden AL curve and SPEED-Bench collector / [Klaud Cold] 新增 MiniMax-M3.1-Flash DSpark 黄金 AL 曲线与 SPEED-Bench 采集脚本 #4425): AL 4.04 at 7 tokens, thinking on (adaptive, the default).infx generatebinds every matrix point to exactly one recipe variant, withSGLANG_SIMULATE_ACC_LEN=4.04.vLLM siblings: #4419 (GB300), #4420 (MI355X), #4421 (B300), #4422 (H100), #4423 (H200), #4426/#4431 (B200), #4433 (GB200).