[TRTLLM-13409][fix] Count async KV completions as benchmark fill progress - #18456
Conversation
…ress Signed-off-by: Xianjie <5410381+qiaoxj07@users.noreply.github.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. WalkthroughBenchmark disaggregated fill tracking now uses generation-transfer state names. The executor records progress from synchronous, Python, and C++ completion signals. The fill gate deduplicates completions and applies the result to retry and stall handling. ChangesDisaggregated generation transfer
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to This localized change extends benchmark fill progress tracking to asynchronous completions without changing public APIs or non-benchmark behavior. It is merge-ready after normal checks and review; no actionable merge-blocking risk remains. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/bot run --disable-fail-fast |
1 similar comment
|
/bot run --disable-fail-fast |
|
PR_Github #70387 [ run ] triggered by Bot. Commit: |
|
PR_Github #70387 [ run ] completed with state
|
|
/bot run --disable-fail-fast |
|
PR_Github #70432 [ run ] triggered by Bot. Commit: |
|
PR_Github #70432 [ run ] completed with state
|
|
/bot run --disable-fail-fast |
1 similar comment
|
/bot run --disable-fail-fast |
|
PR_Github #70471 [ run ] triggered by Bot. Commit: |
|
PR_Github #70471 [ run ] completed with state
|
|
/bot run --disable-fail-fast |
|
PR_Github #70510 [ run ] triggered by Bot. Commit: |
|
PR_Github #70510 [ run ] completed with state
|
|
/bot run --disable-fail-fast |
|
PR_Github #70588 [ run ] triggered by Bot. Commit: |
|
PR_Github #70588 [ run ] completed with state
|
Signed-off-by: Xianjie <5410381+qiaoxj07@users.noreply.github.com>
|
/bot run |
|
PR_Github #70684 [ run ] triggered by Bot. Commit: |
|
PR_Github #70684 [ run ] completed with state
|
JunyiXu-nv
left a comment
There was a problem hiding this comment.
LGTM! Thanks for the fix!
|
/bot run --disable-fail-fast |
1 similar comment
|
/bot run --disable-fail-fast |
|
PR_Github #71127 [ run ] triggered by Bot. Commit: |
|
PR_Github #71129 [ run ] triggered by Bot. Commit: |
|
PR_Github #71127 [ run ] completed with state |
|
PR_Github #71129 [ run ] completed with state
|
|
/bot run --disable-fail-fast |
|
PR_Github #71199 [ run ] triggered by Bot. Commit: |
|
PR_Github #71199 [ run ] completed with state |
Dev Engineer Review
QA Engineer Review
tests/unittest/_torch/executor/test_benchmark_disagg.py:tests/unittest/_torch/executor/test_py_executor.py:_disagg_gen_transfer_made_progress.tests/integration/test_lists/,test-db/,qa/, orwaives.txtchanges were reported.Description
#17202 added a no-progress deadline to the benchmark-disaggregated fill gate, but the executor only fed synchronous receive completions into that deadline. With generation-transfer overlap enabled, asynchronous requests can complete steadily while the watchdog sees no progress and eventually terminates a healthy large fill after the default 600-second window.
This change records synchronous and asynchronous GEN KV completions in one per-iteration progress signal. It supports both transceiver contracts on current
main: Python V2 completion IDs and the C++ runtime's request-state-only completion reporting. The existing model-parallel all-gather propagates that signal before pacing and stall checks, so this adds no collective and does not change non-benchmark execution or public APIs.Related: #17202, #18178.
Test Coverage
pre-commitpassed for all changed files, including isort, YAPF, Ruff, Ruff format, codespell, and repository policy hooks.PR Checklist
Please review the following before submitting your PR:
PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.
PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.
Test cases are provided for new code paths (see test instructions)
If PR introduces API changes, an appropriate PR label is added - either
api-compatibleorapi-breaking. Forapi-breaking, includeBREAKINGin the PR title.Any new dependencies have been scanned for license and vulnerabilities
CODEOWNERS updated if ownership changes
Documentation updated as needed
Update tava architecture diagram if there is a significant design change in PR.
The reviewers assigned automatically/manually are appropriate for the PR.
Please check this after reviewing the above items as appropriate for this PR.
GitHub Bot Help
To see a list of available CI bot commands, please comment
/bot help.