Skip to content

config(dsv4): constrain OpenMP threads for GB300 AgentX / 限制 GB300 AgentX 的 OpenMP 线程数 - #2711

Open
RohitNagraj wants to merge 3 commits into
mainfrom
dsv4-fp4-gb300-dynamo-trt-agentx-omp-threads
Open

config(dsv4): constrain OpenMP threads for GB300 AgentX / 限制 GB300 AgentX 的 OpenMP 线程数#2711
RohitNagraj wants to merge 3 commits into
mainfrom
dsv4-fp4-gb300-dynamo-trt-agentx-omp-threads

Conversation

@RohitNagraj

@RohitNagraj RohitNagraj commented Aug 24, 2026

Copy link
Copy Markdown
Collaborator

Description

Set OMP_NUM_THREADS=1 in both the prefill and decode worker environments across all six DeepSeek-V4-Pro GB300 Dynamo-TensorRT-LLM AgentX recipes. This keeps OpenMP thread creation consistently bounded across the recipe matrix.

Remove the explicit KV_OFFLOADING overrides from the frontend and benchmark environments so the runtime-provided setting is inherited.

Local validation covered YAML parsing, exact-key matrix generation, focused master-to-recipe parity, all six srt-slurm recipe dry runs, and the GB300 launcher contract tests.

中文说明

在全部六个 DeepSeek-V4-Pro GB300 Dynamo-TensorRT-LLM AgentX 配方的预填充和解码工作进程环境中设置 OMP_NUM_THREADS=1,从而在整个配置矩阵中统一限制 OpenMP 线程创建数量。

移除前端和基准测试环境中显式设置的 KV_OFFLOADING,使其继承运行时提供的设置。

本地验证包括 YAML 解析、精确配置键矩阵生成、主配置与配方的定向一致性检查、六个 srt-slurm 配方的 dry-run,以及 GB300 启动器契约测试。

Related Issue

N/A

Type of Change

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

Checklist

  • I have tested my changes locally
  • I have updated documentation if necessary (No documentation change is required for this recipe-only update.)
  • For every change that can affect benchmark performance and every recipe addition or modification, I have appended a new entry to the physical end of perf-changelog.yaml and have not edited historical entries
  • Before merging via reuse, an authorized maintainer (OWNER/MEMBER/COLLABORATOR) has commented /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 sweep label will no longer automatically kick off new sweeps. Remove and re-add the label to force one.

Note

Medium Risk
Recipe-only but alters benchmark worker threading and KV offloading inheritance, which can change measured AgentX performance versus prior sweeps.

Overview
Updates all six DeepSeek-V4-Pro GB300 Dynamo–TensorRT-LLM AgentX srt-slurm recipes with two environment tweaks.

OMP_NUM_THREADS: '1' is added to both prefill_environment and decode_environment so OpenMP thread usage is capped consistently across the recipe matrix.

The explicit KV_OFFLOADING: none entries are removed from frontend and benchmark env blocks so those jobs inherit the runtime-provided KV offloading setting instead of pinning it in YAML.

A perf-changelog.yaml entry documents the change under config key dsv4-fp4-gb300-dynamo-trt-agentx (agentic-coding).

Reviewed by Cursor Bugbot for commit 872b82e. Bugbot is set up for automated code reviews on this repo. Configure here.

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

RohitNagraj added a commit that referenced this pull request Aug 24, 2026
在性能变更日志中补充 PR #2711 链接。
@github-actions

Copy link
Copy Markdown
Contributor

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

2 similar comments
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

为 GB300 AgentX 的预填充和解码工作进程限制 OpenMP 线程数。
在性能变更日志中补充 PR #2711 链接。
让 GB300 AgentX 的前端和基准测试环境继承 KV 卸载设置。
@RohitNagraj
RohitNagraj force-pushed the dsv4-fp4-gb300-dynamo-trt-agentx-omp-threads branch from 3231cae to 872b82e Compare August 27, 2026 18:05
@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

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant