Skip to content

Deprecate 1k1k benchmark configurations - #2263

Merged
adibarra merged 1 commit into
mainfrom
chore/deprecate-1k1k
Jul 18, 2026
Merged

Deprecate 1k1k benchmark configurations#2263
adibarra merged 1 commit into
mainfrom
chore/deprecate-1k1k

Conversation

@adibarra

@adibarra adibarra commented Jul 18, 2026

Copy link
Copy Markdown
Collaborator

As previously discussed, the time has come to deprecate 1k1k. 🫡

Summary

  • Remove all 1k1k fixed-sequence scenarios from the active NVIDIA and AMD master configs.
  • Archive the removed scenarios in:
    • configs/deprecated/nvidia-1k1k-master.yaml
    • configs/deprecated/amd-1k1k-master.yaml
  • Preserve all active 8k1k and agentic configurations.

Verification

  • Active master configs generate 0 fixed-sequence 1k1k jobs.
  • Active master configs generate 1,883 fixed-sequence 8k1k jobs.
  • Deprecated configs generate 1,831 fixed-sequence 1k1k jobs.
  • Verified that the archived and remaining scenarios exactly partition the original configurations.

@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution! Please reach out to respective companies' CODEOWNER to fill in the latest PR_REVIEW_CHECKLIST.md before pinging core maintainer on Slack for review. In order for the signoff PR check bot to trigger, you must follow the PR_REVIEW_CHECKLIST.md template correctly, including the phrase As a PR reviewer and CODEOWNER, I have reviewed this and have.

For PR verification, add the full-sweep-fail-fast label (strongly recommended) to this PR — the benchmark sweep only runs on labeled PRs. Use full-sweep-enabled only if you need matrix jobs to keep running past a failure.

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. See GitHub's docs on re-running failed jobs


感谢你的贡献!请联系相应公司的 CODEOWNER 填写最新的 PR_REVIEW_CHECKLIST.md,然后再在 Slack 上联系核心维护者进行审阅。为了触发 signoff PR 检查机器人,你必须正确遵循 PR_REVIEW_CHECKLIST.md 模板,包括保留英文语句 As a PR reviewer and CODEOWNER, I have reviewed this and have

如需进行 PR 验证,请为此 PR 添加 full-sweep-fail-fast 标签(强烈推荐)— 基准测试 sweep 仅在带有标签的 PR 上运行。仅当需要矩阵任务在失败后继续运行时才使用 full-sweep-enabled

PR 作者有责任确保合并后所有 GitHub Action 任务完全通过。 很多时候失败只是偶发抖动(flake),重新运行失败的任务即可解决。参见 GitHub 关于重新运行失败任务的文档

@adibarra
adibarra merged commit 0094291 into main Jul 18, 2026
13 checks passed
@adibarra
adibarra deleted the chore/deprecate-1k1k branch July 18, 2026 01:50
Comment thread configs/amd-master.yaml
Comment thread configs/amd-master.yaml
Ankur-singh added a commit that referenced this pull request Aug 6, 2026
…-trt / 移除已弃用的 Single-turn 1k1k 场景

Single-turn 1k1k (isl 1024 / osl 1024) is deprecated for all models since
2026-07-17 (#2263) per MODELS.md, and the deprecation was enacted on
2026-08-04 by #2493, which removed 54 config keys from the active master
configs. This submission still added a 1k1k scenario, so it is removed here.

- Delete the 9 disagg 1k1k STP recipes under
  benchmarks/multi_node/srt-slurm-recipes/trtllm/qwen3.5/gb300-fp4/disagg/1k1k/
- Remove the isl 1024 / osl 1024 scenario (9 search-space points) from the
  qwen3.5-fp4-gb300-dynamo-trt block in configs/nvidia-master.yaml
- Align the perf-changelog entry to describe an 8k1k-only submission

The Single-turn 8k1k half is unchanged: 9 recipes and 9 search-space points
remain byte-identical.

中文:根据 MODELS.md,Single-turn 1k1k(isl 1024 / osl 1024)自 2026-07-17
起对所有模型弃用(#2263),并已于 2026-08-04 由 #2493 正式执行(从活跃主配置中
移除了 54 个 config key)。本次提交仍新增了 1k1k 场景,故在此移除:删除
gb300-fp4/disagg/1k1k/ 下的 9 个 STP recipe,从 configs/nvidia-master.yaml 的
qwen3.5-fp4-gb300-dynamo-trt 块中删除 isl 1024 / osl 1024 场景及其 9 个搜索空间
配置点,并同步修改 perf-changelog 描述为仅 8k1k。Single-turn 8k1k 部分保持不变,
9 个 recipe 与 9 个搜索空间配置点逐字节保留。
adibarra added a commit that referenced this pull request Aug 10, 2026
…arks / [NVIDIA] 添加 GB300 Qwen3.5 NVFP4 Dynamo-TensorRT-LLM 分离式基准测试 (#2206)

* add dynamo trtllm gb300 qwen3.5 nvfp4 recipes

* update PR link

* update PR link

* fix no preflight

* chore: drop deprecated Single-turn 1k1k from qwen3.5-fp4-gb300-dynamo-trt / 移除已弃用的 Single-turn 1k1k 场景

Single-turn 1k1k (isl 1024 / osl 1024) is deprecated for all models since
2026-07-17 (#2263) per MODELS.md, and the deprecation was enacted on
2026-08-04 by #2493, which removed 54 config keys from the active master
configs. This submission still added a 1k1k scenario, so it is removed here.

- Delete the 9 disagg 1k1k STP recipes under
  benchmarks/multi_node/srt-slurm-recipes/trtllm/qwen3.5/gb300-fp4/disagg/1k1k/
- Remove the isl 1024 / osl 1024 scenario (9 search-space points) from the
  qwen3.5-fp4-gb300-dynamo-trt block in configs/nvidia-master.yaml
- Align the perf-changelog entry to describe an 8k1k-only submission

The Single-turn 8k1k half is unchanged: 9 recipes and 9 search-space points
remain byte-identical.

中文:根据 MODELS.md,Single-turn 1k1k(isl 1024 / osl 1024)自 2026-07-17
起对所有模型弃用(#2263),并已于 2026-08-04 由 #2493 正式执行(从活跃主配置中
移除了 54 个 config key)。本次提交仍新增了 1k1k 场景,故在此移除:删除
gb300-fp4/disagg/1k1k/ 下的 9 个 STP recipe,从 configs/nvidia-master.yaml 的
qwen3.5-fp4-gb300-dynamo-trt 块中删除 isl 1024 / osl 1024 场景及其 9 个搜索空间
配置点,并同步修改 perf-changelog 描述为仅 8k1k。Single-turn 8k1k 部分保持不变,
9 个 recipe 与 9 个搜索空间配置点逐字节保留。

* Correct kv-p2p-transfer metadata and the srt-slurm changelog reference

Two label defects, no behaviour change:

- configs/nvidia-master.yaml declared kv-p2p-transfer: nixl, but all nine
  retained recipes set cache_transceiver_config.backend: UCX on both prefill
  and decode. That value is propagated verbatim into every result row as
  kv_p2p_transfer, so each published point was labelled NIXL while running
  UCX. Corrected to ucx to describe what actually runs.

- The perf-changelog entry said the runner clones srt-slurm@sa-submission-q2-2026
  while launch_gb300-nv.sh checks out the immutable tag v1.0.29 on this path.
  Corrected, and the --no-preflight change this PR also makes is now recorded.

---------

Co-authored-by: Ankur-singh <ankusingh@nvidia.com>
Co-authored-by: adibarra <93070681+adibarra@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

1 participant