Repository navigation
[K3.1-Pro] vLLM B300: low-latency decode and SGLang draft depths / [K3.1-Pro] vLLM B300:启用低延迟 decode 并对齐 SGLang 草稿深度 - #4833
Conversation
Turn on decode_backend=latency_specialized at every point, run c1-c2 at plain TP8 instead of TP8 x DCP8, and raise the c1 and c70 graph caps to 16 and 432 so the full decode step is captured. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0188HSzNcNLyDbocjggjUSvq
…7200 s The latency_specialized decode path adds a second FlashInfer autotune pass at startup; on a local GB300 run it took ~40 min to become ready. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0188HSzNcNLyDbocjggjUSvq
DSpark now drafts 7 tokens through c8, 6 at c16, 5 at c24-c40 and 4 from c48, the same draft counts as the SGLang DFLASH recipe, and each decode graph cap covers max-num-seqs x (1 + drafts). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0188HSzNcNLyDbocjggjUSvq
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0188HSzNcNLyDbocjggjUSvq
💡 Codex ReviewInferenceX/inferencex-e2e/perf-changelog.yaml Line 12052 in 55582cd When maintainers run the required reuse merge, AGENTS.md reference: AGENTS.md:L89-L89 These lines are a header for the complete override section and restate admission, draft counts, graph sizing, and the TP/DCP topology rather than briefly explaining one specific setting. The repository's mandatory comment convention explicitly forbids headers describing recipes, topologies, or overrides, so remove this summary and retain only value-specific rationale beside the affected keys. AGENTS.md reference: AGENTS.md:L54-L58 ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
…ency-decode # Conflicts: # inferencex-e2e/perf-changelog.yaml
…ency-decode # Conflicts: # inferencex-e2e/perf-changelog.yaml
|
Dispatched trusted sweep run for approved external revision 已为获批的外部提交 |
Resolve the perf-changelog conflict by keeping main's new entries and appending the B300 vLLM entry last. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0188HSzNcNLyDbocjggjUSvq
The kimi-k31 image launches the wide (65-320 row) MoE experts on 152 CTAs that must all be co-resident; a B300 has 148 SMs, so every point whose decode graphs exceed 64 rows (c8-c70) failed engine init. Keep latency_specialized where graphs stay within 64 rows and run the stock decode above. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0188HSzNcNLyDbocjggjUSvq
|
Dispatched trusted sweep run for approved external revision 已为获批的外部提交 |
|
/use 42150239586 |
|
@cquil11 staged run 42150239586. This run remains available across future |
|
/use 42150239586 |
|
@cquil11 staged run 42150239586. This run remains available across future |
…ency-decode # Conflicts: # inferencex-e2e/perf-changelog.yaml
|
Ingest report — ✅ Results ingested into the Ingest workflow · Merge Ingest run · Benchmark source run
benchmarkFiles 12, rawBenchmarkRows 23, coveredByPerJobFiles 12, purgedPoints 0, failedRunRows 0, runStatsNew 0, runStatsDuplicate 0, evalSamplesNew 1319, gpuMetricSamplesNew 554880, powerPublicationPoints 11, 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 时本评论会原地更新。 |
Tunes
kimik3.1-fp4-b300-vllm-agentic-dspark(Kimi-K3.1-Pro, B300, vLLM, DSpark):--additional-config '{"decode_backend":"latency_specialized"}'at every point (the vLLM K3.1 recipe's fused CuTe DSL decode path).max-num-seqs x (1 + drafts).VLLM_ENGINE_READY_TIMEOUT_Sand the health check go to 7200 s, because the specialized path adds an autotune pass.Local A/B on GB300 (TP8 over two trays, 20 min per point, previous draft depths):
All 11 points started and finished with the previous draft depths. The new draft depths are still being checked locally (c8, c56, c70).
中文
调整
kimik3.1-fp4-b300-vllm-agentic-dspark(Kimi-K3.1-Pro,B300,vLLM,DSpark):--additional-config '{"decode_backend":"latency_specialized"}',即 vLLM K3.1 recipe 的融合 CuTe DSL decode 路径。max-num-seqs x (1 + drafts)。VLLM_ENGINE_READY_TIMEOUT_S和 health check 提高到 7200 秒。本地 GB300 A/B(两个 tray 组成 TP8,每点 20 分钟,旧草稿深度)见上表:c1 的 ITL p50 从 5.32 ms 降到 2.77 ms,c32 从 17.86 ms 降到 15.16 ms,c70 从 37.09 ms 降到 33.09 ms。
旧草稿深度下 11 个点都能正常启动并跑完;新草稿深度仍在本地验证(c8、c56、c70)。
🤖 Generated with Claude Code
https://claude.ai/code/session_0188HSzNcNLyDbocjggjUSvq