Skip to content

[codex] Update MiniMax M3 B200 EAGLE3 FlashInfer image#1832

Open
cquil11 wants to merge 9 commits into
mainfrom
chore/b200-m3-mtp-flashinfer
Open

[codex] Update MiniMax M3 B200 EAGLE3 FlashInfer image#1832
cquil11 wants to merge 9 commits into
mainfrom
chore/b200-m3-mtp-flashinfer

Conversation

@cquil11

@cquil11 cquil11 commented Jun 18, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • update minimaxm3-fp8-b200-vllm-mtp to vllm/vllm-openai:minimax-m3-0618
  • enable FlashInfer TRT-LLM attention with FP8 indexer KV and KV cache
  • use TRITON_ATTN for the EAGLE3 drafter and the image's default FlashInfer TRT-LLM MoE backend

Validation

  • benchmark script passes bash -n
  • MiniMax M3 B200-DGXC vLLM sweep generation succeeds

Note

Medium Risk
Benchmark-only changes, but they alter attention/MoE backends and patch installed vLLM at job start—incorrect flags or patch anchors would break engine init on B200 MTP sweeps.

Overview
Brings minimaxm3-fp8-b200-vllm-mtp in line with the non-MTP B200 0618 vLLM image: CI image tag, benchmark serve flags, and docs/changelog.

The MTP benchmark script now uses FlashInfer TRT-LLM attention with FP8 indexer KV and KV cache, drops explicit Marlin MoE on TP-only runs (image default MoE), and applies the same runtime MSA prefill .contiguous() patch on sparse_attention_msa.py as the base B200 recipe. The EAGLE3 draft head attention backend changes from FLASH_ATTN to TRITON_ATTN so spec decode matches the new target stack.

Reviewed by Cursor Bugbot for commit 6e6fdc9. Bugbot is set up for automated code reviews on this repo. Configure here.

@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution! For vLLM & SGLang, please ensure that your recipes is similar to the official vLLM recipes and/or the SGLang cookbook

If it is not, please create a PR first before we can merge your single node PR into the master branch. Let's ensure that the documentation is first class such that the entire ML community can benefit from your hard work! Thank you

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. If re-running failed jobs is attempted, PR authors are responsible for ensuring it passes. See GitHub's docs on re-running failed jobs: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow

As a rule of thumb, generally, PR authors should request a review & get a PR approval from the respective companies' CODEOWNERS before requesting a review from core maintainers.

If additional help is needed, PR authors can reach out to core maintainers over Slack.

@github-actions

Copy link
Copy Markdown
Contributor

@SemiAnalysisAI SemiAnalysisAI deleted a comment from cquil11 Jun 18, 2026
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

5 similar comments
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@Oseltamivir

Copy link
Copy Markdown
Collaborator

/reuse-sweep-run

@Oseltamivir Oseltamivir requested a review from Ankur-singh as a code owner June 23, 2026 03:42

@Oseltamivir Oseltamivir left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

lgtm

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.

2 participants