Skip to content

[VideoGenX] sweep H3 latency on 2, 4 and 8 H100 GPUs / [VideoGenX] 在 2、4、8 张 H100 上扫描 H3 延迟 - #4857

Merged
edwingao28 merged 5 commits into
mainfrom
feat/h3-h100-gpu-count-sweep
Nov 6, 2026
Merged

edwingao28 merged 5 commits into
mainfrom
feat/h3-h100-gpu-count-sweep

Conversation

@edwingao28

@edwingao28 edwingao28 commented Nov 6, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

H100 has one MiniMax-H3 C1 video point, on 4 GPUs, so it cannot show how video latency scales with GPU count.

Changes:

  • h3-bf16-h100-sglang-video adds C1 points on 2 and 8 GPUs beside the existing 4-GPU point. H100 starts at 2 GPUs because the model does not fit one 80 GB GPU.
  • H100 recipes: SGLang runs TP2 with Ulysses 1 on 2 GPUs (serving-client-tp2.yaml) and Ulysses 4 on 8 GPUs (serving-client-tp2-ulysses4.yaml). The 4-GPU point keeps its existing recipe.
  • Docs (MODELS.md, video-generation.md) list the new points.

Results: MiniMax-H3 C1, h3-v2.yaml release-v1 (20 clips, 1344x768, 124 frames, 49 steps), SGLang v0.5.23, qualifying sweep 42177029852 attempt 1 at 62dd0294a.

GPUs Job Valid clips Client-ready p50 (s) Speedup vs 2 GPUs Total GPU power (W) GPU energy per clip (Wh)
2 job 20/20 148.2 1.00x 1,347 55.5
4 job 20/20 73.4 2.02x 2,767 56.4
8 job 20/20 39.2 3.78x 5,511 60.2
  • The PR matrix plans exactly these 3 jobs and no evals.
  • validate-video-results accepted all 3 native deployments, the result bundles carry the planned recipe fingerprints, and every server loaded the pinned MiniMax-H3 snapshot.
  • Every job has valid power telemetry.
  • The table reports each job's client-ready p50, from submit to downloaded video, which is the latency the dashboard plots. The job summary's latency_median_seconds also counts client-side media validation, which adds 0.59 to 0.62 s to each median.
  • The client polls job status every 0.5 s and sees a finished job only at the next poll, so each point includes 0 to 0.5 s of polling delay. [VideoGenX] poll H3 jobs every 0.1 s and rerun all four SKUs / [VideoGenX] H3 任务改为每 0.1 s 轮询并重跑四种硬件 #4904 polls every 0.1 s and reruns all four SKUs.

Related: #4818 (MI355X), #4852 (B200) and #4856 (H200) add the other SKUs. Whichever merges later reconciles the shared doc sentence and the changelog tail.

PR checklist and change type

Type of Change

  • Bug fix
  • New feature
  • Configuration change
  • Documentation update
  • Other (please describe)

Checklist

  • I have completed the AI model disclosure and kept it current
  • I have tested my changes locally
  • I have updated documentation if necessary
  • If python -m infx.matrix.changed --base origin/main lists affected config keys, I have appended one new entry covering them to the physical end of inferencex-e2e/perf-changelog.yaml; if it lists none, I have added none. I have not edited historical entries
  • If this PR appends an inferencex-e2e/perf-changelog.yaml entry, it carries exactly one primary sweep label (a maintainer applies it on fork PRs): full-sweep-fail-fast (recommended), full-sweep-enabled, or non-canary-full-sweep-enabled. Optional modifiers all-evals, evals-only, and agentx-fast require a primary label; the last two block reuse while applied.
  • Before merging via reuse, an authorized maintainer (OWNER/MEMBER/COLLABORATOR) has commented /use <run_id> (or the legacy /reuse-sweep-run) on this PR. Do this only once there is a final full sweep that is all green with evals passing, since after this comment the primary sweep label will no longer automatically kick off new sweeps. Remove and re-add the primary sweep label to force a new sweep.

@github-actions

github-actions Bot commented Nov 6, 2026

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 任务通过。临时性失败通常可以通过重新运行恢复;参见重新运行失败任务的说明。

@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.

Code review found no issues

No high-confidence issues detected in this change.

This review covers commit 56e7c0d, which is no longer the latest commit on this pull request; later commits are not covered by it.

@edwingao28 edwingao28 added the full-sweep-fail-fast Full sweep with canary gate; first failure cancels the rest of that matrix (recommended) label Nov 6, 2026
@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

…t-sweep

# Conflicts:
#	inferencex-e2e/perf-changelog.yaml
@edwingao28

Copy link
Copy Markdown
Collaborator Author

/use 42177029852

@github-actions

github-actions Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

@edwingao28 staged run 42177029852.

This run has no staged performance curves.

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

…t-sweep

# Conflicts:
#	inferencex-e2e/perf-changelog.yaml
…t-sweep

# Conflicts:
#	inferencex-e2e/docs/MODELS.md
#	inferencex-e2e/docs/video-generation.md
#	inferencex-e2e/perf-changelog.yaml
@edwingao28
edwingao28 merged commit dd085d0 into main Nov 6, 2026
29 checks passed
@edwingao28
edwingao28 deleted the feat/h3-h100-gpu-count-sweep branch November 6, 2026 09:54
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