Skip to content

fix(ci): pin linear CUDA-graph sizing distribution for gpt_grpo_*_8b_throughput - #5242

Closed
Connor-XY wants to merge 1 commit into
NVIDIA:mainfrom
Connor-XY:yxu1/grpo-cudagraph-linear-distribution
Closed

fix(ci): pin linear CUDA-graph sizing distribution for gpt_grpo_*_8b_throughput#5242
Connor-XY wants to merge 1 commit into
NVIDIA:mainfrom
Connor-XY:yxu1/grpo-cudagraph-linear-distribution

Conversation

@Connor-XY

@Connor-XY Connor-XY commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

What

Pin the linear CUDA-graph sizing distribution for the GRPO throughput tests:

  • gpt_grpo_tp4_pp1_dp2_8b_throughput
  • gpt_grpo_tp4_pp1_dp2_8b_cudagraphs_throughput

via --inference-dynamic-batching-cuda-graph-sizing-distribution: linear.

Why

Both fail their mem-allocated-bytes guardrail in CI: peak ~69.2 GB vs ~60.9 GB golden (+13.6%, tol 10%). lm-loss passes — training is numerically correct; only peak memory grew.

Bisected (scanned every GRPO run May 18→Jun 5) to a single commit — last-pass bdcaf267 → first-fail 16b71941, the only commit between:

PR #3509 — "Change the cudagraph distribution from linearly to exponentially-decreasing + grid for mixed prefill"

It made exponential the default sizing distribution and added a mixed-prefill grid. This pins the pre-#3509 (linear) behavior for these tests.

Caveat (validate on CI)

These recipes use --inference-dynamic-batching-num-cuda-graphs 1, so the sizing distribution mainly selects the single captured graph size; #3509 also added the mixed-prefill grid (--inference-dynamic-batching-cuda-graph-mixed-prefill-count, default 16), which may be a separate memory driver. If linear alone doesn't bring peak memory under the 10 % bound, the follow-up lever is reducing mixed-prefill-count — or the inference team confirms exponential+grid is the intended default and the golden is rebaselined. (Couldn't reproduce locally — GRPO needs the Qwen3-8B ckpt + RL rollout harness.)

🤖 Generated with Claude Code

@copy-pr-bot

copy-pr-bot Bot commented Jun 9, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

…throughput

gpt_grpo_tp4_pp1_dp2_8b_throughput (+ _cudagraphs variant) fail their
mem-allocated-bytes guardrail: peak ~69.2GB vs ~60.9GB golden (+13.6%, tol 10%).
lm-loss passes -- training is numerically correct; only peak memory grew.

Bisected the regression to a single commit (last-pass bdcaf26 -> first-fail
16b7194, the only commit between): PR NVIDIA#3509 "Change the cudagraph distribution
from linearly to exponentially-decreasing + grid for mixed prefill", which made
`exponential` the default sizing distribution and added a mixed-prefill grid.

Set --inference-dynamic-batching-cuda-graph-sizing-distribution=linear to pin the
pre-NVIDIA#3509 behavior for these tests.

Caveat: these recipes use --inference-dynamic-batching-num-cuda-graphs 1, so the
sizing distribution mainly selects the single captured graph size; NVIDIA#3509 also added
the mixed-prefill grid (--inference-dynamic-batching-cuda-graph-mixed-prefill-count,
default 16) which may be a separate memory driver. If `linear` alone does not bring
peak memory under the 10% bound in CI, the follow-up lever is reducing the
mixed-prefill-count (or the inference team confirms exponential+grid is the intended
default and the golden is rebaselined).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Connor-XY
Connor-XY force-pushed the yxu1/grpo-cudagraph-linear-distribution branch from 8d52f83 to 7207238 Compare June 9, 2026 22:32
@Connor-XY
Connor-XY marked this pull request as ready for review June 9, 2026 22:34
@Connor-XY

Copy link
Copy Markdown
Contributor Author

/ok to test 7207238

@Connor-XY

Copy link
Copy Markdown
Contributor Author

Superseded by #5253.

@Connor-XY Connor-XY closed this Jun 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants