Repository navigation
[K3.1-Pro] Add GB200 SGLang 1P1D points with an EP16 MegaMoE decode - #4929
Conversation
|
Thanks for the contribution!
中文感谢你的贡献!
|
| # EP16 decode with DeepGEMM MegaMoE (MXFP8 dispatch, BF16 combine) frees about 5 GB of | ||
| # weights per GPU, which raises the decode KV pool from 878k to 1.18M tokens per rank. |
There was a problem hiding this comment.
🟡 nit (optional): The comment above the new override is a header with past results, which AGENTS.md comment rules forbid. It describes the whole override and quotes the measured KV pool change "from 878k to 1.18M tokens". Those numbers are history that belongs in the PR or perf-changelog.yaml. Fix: drop the header, or keep one short line on the line it explains (for example, why expert-parallel-size: 16 is set) without the measured before/after figures.
Why this was flagged
AGENTS.md:56-58, which CLAUDE.md delegates to, says "No header comments describing a file, topology, config, recipe, override, or section" and "No history: ... or past results". The new lines at disagg-variants.yaml:216-217 sit above override_1p1d_tp16_ep16 and describe the override as a whole. They also record a measured result, the decode KV pool growing "from 878k to 1.18M tokens per rank". That figure will go stale as soon as the image or memory settings change. The other overrides in this file (c16, c32, c48) have no header comment. The base branch has no such comment.
Verification: disagg-variants.yaml:216-217 adds a top-level comment directly above override_1p1d_tp16_ep16: (line 218). AGENTS.md:56 forbids "header comments describing a file, topology, config, recipe, override, or section", and AGENTS.md:57 forbids "past results". The comment describes the whole override and records measured KV pool figures (878k to 1.18M). Nothing breaks at runtime.
…lang-megamoe # Conflicts: # inferencex-e2e/perf-changelog.yaml
|
View unofficial run (performance): https://inferencex.semianalysis.com/inference?unofficialRun=42530422785 View unofficial run (accuracy): https://inferencex.semianalysis.com/evaluation?unofficialRun=42530422785 |
|
/use 42530422785 |
|
@cquil11 staged run 42530422785. This run remains available across future |
|
/reuse-sweep-run 42530422785 |
# Conflicts: # inferencex-e2e/perf-changelog.yaml
|
Ingest report — ✅ Results ingested into the Ingest workflow · Merge Ingest run · Benchmark source run
benchmarkFiles 3, rawBenchmarkRows 3, coveredByPerJobFiles 0, purgedPoints 0, failedRunRows 0, runStatsNew 0, runStatsDuplicate 0, evalSamplesNew 0, gpuMetricSamplesNew 587952, powerPublicationPoints 3, 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 时本评论会原地更新。 |
Adds three points to Kimi-K3.1-Pro GB200 SGLang 1P1D AgentX from #4804 at conc 64, 76 and 96, using an EP16 decode on DeepGEMM MegaMoE. This is append-only: the image and the existing c16, c32 and c48 points are unchanged.
moe-a2a-backend: megamoe(MXFP8 dispatch, BF16 combine). Sharding the experts frees about 5 GB of weights per GPU, so the decode KV pool grows from 878k to 1.18M tokens per rank.Test run
Run 42201408790 ran the same recipe at c76. Compared with #4804's sweep: