Skip to content

[Klaud Cold] minimaxm31flash-fp4-mi355x-sglang-agentic-dspark: disable sparse index top-k sharing (SGLANG_MINIMAX_M3_INDEX_TOPK_FREQ=1) - #4469

Merged
Oseltamivir merged 3 commits into
mainfrom
exp/minimaxm31flash-mi355x-sgl-topk-freq1
Oct 25, 2026
Merged

Oseltamivir merged 3 commits into
mainfrom
exp/minimaxm31flash-mi355x-sgl-topk-freq1

Conversation

@Oseltamivir

Copy link
Copy Markdown
Collaborator

Follow-up to #4445. Sets SGLANG_MINIMAX_M3_INDEX_TOPK_FREQ=1 on the MI355X SGLang MiniMax-M3.1-Flash AgentX recipe.

SGLang defaults this to 2 on ROCm (sgl-project/sglang#36527, environ.py#L2033-L2039): each pair of sparse-attention layers shares one index top-k selection. NVIDIA always runs with 1. Setting 1 here makes every layer compute its own selection, matching NVIDIA and removing the stale-selection approximation, so the throughput and eval comparison against #4445 shows what sharing buys.

Only the env var changes; search space, image and serve flags are unchanged.

@Oseltamivir
Oseltamivir requested a review from a team October 24, 2026 16:05
@Oseltamivir Oseltamivir added the full-sweep-fail-fast Full sweep with canary gate; first failure cancels the rest of that matrix (recommended) label Oct 24, 2026
@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 non-canary-full-sweep-enabled Run the full sweep without the canary gate (full search space, no trim) and removed full-sweep-fail-fast Full sweep with canary gate; first failure cancels the rest of that matrix (recommended) labels Oct 24, 2026
Comment thread inferencex-e2e/perf-changelog.yaml Outdated
- minimaxm31flash-fp4-mi355x-sglang-agentic-dspark
description:
- "Set SGLANG_MINIMAX_M3_INDEX_TOPK_FREQ=1 on MI355X SGLang MiniMax-M3.1-Flash AgentX: every sparse layer computes its own index top-k instead of SGLang's ROCm default of sharing one across each pair of layers (sgl-project/sglang#36527)."
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 new changelog entry will fail the perf-changelog validator on this PR's CI run, which blocks the benchmark from being scheduled and merged. pr-link: TBD is neither the canonical PR URL nor an accepted placeholder. validate_perf_changelog.py:22-25 only accepts "XXX" or "https://github.com/SemiAnalysisAI/InferenceX/pull/XXX". Fix: set pr-link: XXX, or use the real https://github.com/SemiAnalysisAI/InferenceX/pull/<n>. The merge tooling then rewrites the XXX placeholder to the canonical link.

Why this was flagged

The PR appends a block ending in pr-link: TBD at perf-changelog.yaml:11108. On a PR run, validate_added_pr_link in infx/workflows/validate_perf_changelog.py:139-150 checks every added entry. It raises ChangelogValidationError("new PR entry must use '...pull/' or an XXX placeholder; found 'TBD'") unless the link is in PR_LINK_PLACEHOLDERS {"XXX", ".../pull/XXX"} or equals the expected PR URL. On a main-branch run the CANONICAL_PR_LINK regex rejects it as well. The placeholder canonicalizer in prepare_perf_changelog_merge.py also only handles the XXX placeholders (its tests use "XXX"), so nothing rewrites TBD on merge. The base branch has no such entry. CONTRIBUTING.md:206 documents the .../pull/XXX form, and none of the other 11,000+ lines of entries uses TBD.

Verification: Trigger: merging through the supported reuse path (merge_with_reuse) while the entry still has pr-link: TBD. TBD passes PR CI and the sweep is still scheduled. compare_entries(base, head, pr_number) (prepare_perf_changelog_merge.py:88) calls validate_added_pr_link (validate_perf_changelog.py:193). That raises because 'TBD' is not in PR_LINK_PLACEHOLDERS (lines 22-25).

@github-actions

github-actions Bot commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor

@Oseltamivir

Copy link
Copy Markdown
Collaborator Author

/use 40110172586

@github-actions

github-actions Bot commented Oct 25, 2026 •

Copy link
Copy Markdown
Contributor

@Oseltamivir staged run 40110172586.

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

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

Labels

non-canary-full-sweep-enabled Run the full sweep without the canary gate (full search space, no trim)

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant