Skip to content

chore(agentic): rerun DSV4 SGLang with standard warmup#2179

Closed
cquil11 wants to merge 7 commits into
mainfrom
agent/rerun-dsv4-sglang-agentic-warmup
Closed

chore(agentic): rerun DSV4 SGLang with standard warmup#2179
cquil11 wants to merge 7 commits into
mainfrom
agent/rerun-dsv4-sglang-agentic-warmup

Conversation

@cquil11

@cquil11 cquil11 commented Jul 13, 2026

Copy link
Copy Markdown
Collaborator

PR #2112 ran these SGLang agentic configs without the accelerated warmup stage.

This changelog-only PR reruns B200 and B300 with the standard regular warmup followed by the 600-second accelerated warmup.

Tests:

  • python utils/validate_perf_changelog.py --base-ref origin/main --head-ref HEAD
  • 32 targeted changelog tests passed

@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 关于重新运行失败任务的文档

@cquil11 cquil11 force-pushed the agent/rerun-dsv4-sglang-agentic-warmup branch from f149e15 to f9dba8b Compare July 13, 2026 21:10
@cquil11 cquil11 marked this pull request as ready for review July 13, 2026 21:46
@cquil11 cquil11 requested a review from a team July 13, 2026 21:46
@cquil11 cquil11 added full-sweep-enabled NVIDIA agentx AgentX benchmarks, recipes, and infrastructure and removed full-sweep-fail-fast labels Jul 13, 2026
@claude

claude Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Claude finished @cquil11's task in 1m 1s —— View job


Review

  • Gather context (diff vs origin/main)
  • Verify changelog entry placement and referenced config keys
  • Run utils/validate_perf_changelog.pycould not run (command not in allowed tools); verified manually instead
  • Post review summary

LGTM - no blocking issues found

This is a changelog-only PR (+7 lines in perf-changelog.yaml). Verified:

  • The new entry is appended at the very end of the file (correct chronological position).
  • Both config keys (dsv4-fp4-b200-sglang-agentic-hicache, dsv4-fp4-b300-sglang-agentic-hicache) exist in configs/nvidia-master.yaml (lines 14075 and 14097).
  • The pr-link correctly points to this PR (chore(agentic): rerun DSV4 SGLang with standard warmup #2179), and the entry format matches existing entries.

Note: I couldn't execute python utils/validate_perf_changelog.py due to tool permission restrictions in this environment, so validation was done by manual inspection. The author reports the validator and 32 targeted changelog tests passed locally.

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

LGTM — changelog-only entry documenting a rerun, consistent with the established append pattern in this file.

What was reviewed: confirmed the two config-keys (dsv4-fp4-b200/b300-sglang-agentic-hicache) already exist and were introduced in PR #2112; this entry follows the same append-only changelog convention as other rerun entries (e.g. #2137, #2169) rather than mutating the prior entry. No code, recipe, or config files are touched.

Extended reasoning...

Overview

The diff touches only perf-changelog.yaml, appending a single new changelog entry for two existing config-keys (dsv4-fp4-b200-sglang-agentic-hicache, dsv4-fp4-b300-sglang-agentic-hicache). No recipe scripts, master-config entries, or benchmark code are modified. The entry documents that these configs were rerun with a standardized warmup procedure (regular trajectory warmup + 600s accelerated cache-pressure warmup), per the PR description referencing PR #2112 which originally ran them without the accelerated warmup stage.

Security risks

None. This is a plain-text YAML changelog entry with no executable content, no secrets, and no interaction with auth/crypto/permissions code.

Level of scrutiny

Minimal scrutiny is warranted — this is the same append-only changelog pattern used repeatedly elsewhere in this file (e.g. PR #2137, #2169) for documenting reruns/bumps. I verified the referenced config-keys already exist in the file (introduced by PR #2112) and that this PR adds a new entry rather than editing the prior one, which matches the file's convention of accumulating history rather than mutating past entries.

Other factors

The PR description states the changelog validator (validate_perf_changelog.py) was run and 32 targeted tests passed. No outstanding review comments exist in the timeline beyond the automated recipe-reminder bot message. The bug hunting system found no issues, and there is no logic or code surface here to exercise beyond the YAML format itself.

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

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

Labels

agentx AgentX benchmarks, recipes, and infrastructure NVIDIA

Projects

Development

Successfully merging this pull request may close these issues.

1 participant