[None][refactor] Remove TensorRT performance baseline and update to PyTorch only - #15256
Conversation
…yTorch only - Deleted `base_perf.csv` as TensorRT performance stages are no longer supported. - Updated scripts and documentation to reference `base_perf_pytorch.csv` for performance benchmarking. - Adjusted performance check logic to reflect the removal of TensorRT metrics. Signed-off-by: yufeiwu-nv <230315618+yufeiwu-nv@users.noreply.github.com>
📝 WalkthroughWalkthroughThis PR consolidates performance validation infrastructure to use only the PyTorch baseline. It removes TensorRT perf baseline selection logic from Jenkins CI configuration and the perf validation script, hardcodes PyTorch baseline usage, removes the corresponding TensorRT perf test stage, and updates documentation and user-facing messages to reflect the change. ChangesTensorRT Perf Baseline Removal
🎯 1 (Trivial) | ⏱️ ~4 minutes 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/bot run |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@tests/integration/defs/perf/README.md`:
- Line 45: The markdown line starting with "** In the CI, `<base_perf_csv_path>`
is the `base_perf_pytorch.csv` file path mentioned above." has an opening bold
marker but no closing marker; fix it by closing the emphasis (e.g., add trailing
"**" or remove the opening "**") so the line becomes properly balanced around
the intended emphasized text (refer to the literal string "<base_perf_csv_path>"
in the README content).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 8aa497cf-51bd-42ec-b321-513621f98b16
⛔ Files ignored due to path filters (1)
tests/integration/defs/perf/base_perf.csvis excluded by!**/*.csv
📒 Files selected for processing (4)
jenkins/L0_Test.groovyjenkins/scripts/slurm_run.shtests/integration/defs/perf/README.mdtests/integration/defs/perf/sanity_perf_check.py
|
PR_Github #53540 [ run ] triggered by Bot. Commit: |
Signed-off-by: yufeiwu-nv <230315618+yufeiwu-nv@users.noreply.github.com>
|
/bot run |
|
PR_Github #53548 [ run ] triggered by Bot. Commit: |
|
PR_Github #53540 [ run ] completed with state |
|
PR_Github #53548 [ run ] completed with state
|
|
/bot run |
|
PR_Github #53753 [ run ] triggered by Bot. Commit: |
|
PR_Github #53753 [ run ] completed with state
|
|
/bot run --disable-fail-fast |
|
PR_Github #53820 [ run ] triggered by Bot. Commit: |
|
PR_Github #53820 [ run ] completed with state
|
…#15166) NVIDIA#15166 was temporarily reverted in NVIDIA#15310. Reapply it here so the TensorRT perf test removal in l0_perf.yml lands together with the TensorRT stage/baseline cleanup in this PR, keeping the test list and Jenkins perf stages consistent. Signed-off-by: yufeiwu-nv <230315618+yufeiwu-nv@users.noreply.github.com>
|
/bot run |
|
/bot skip --comment "only test modify" |
|
PR_Github #54228 [ run ] triggered by Bot. Commit: |
|
PR_Github #54229 [ skip ] triggered by Bot. Commit: |
|
PR_Github #54229 [ skip ] completed with state |
base_perf.csvas TensorRT performance stages are no longer supported.base_perf_pytorch.csvfor performance benchmarking.Signed-off-by: yufeiwu-nv 230315618+yufeiwu-nv@users.noreply.github.com
Summary by CodeRabbit
Chores
Documentation
Description
Test Coverage
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.