[None][test] add metric for trtllm-bench#14178
Conversation
|
/bot skip --comment "skip test as just adding metrics" |
📝 WalkthroughWalkthroughThis PR migrates the perf testing infrastructure from using a single ChangesPerf Metric Type Migration
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
tests/integration/defs/perf/test_perf.py (1)
1-1:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winUpdate the SPDX copyright year.
This file is modified in this PR, but the header still ends at 2025. Please bump it to 2026 to match the latest modification year. As per coding guidelines, "Include NVIDIA copyright header on all new files; update year on modified files".
🤖 Prompt for 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. In `@tests/integration/defs/perf/test_perf.py` at line 1, Update the SPDX header year in the file's top comment by changing the copyright range end from 2025 to 2026; specifically modify the SPDX line (the header comment starting with "# SPDX-FileCopyrightText") in tests/integration/defs/perf/test_perf.py so it reads 2022-2026.
🤖 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/test_perf.py`:
- Around line 483-486: The metrics map is missing threshold entries for the new
bench throughput metrics, causing _get_metrics() (which calls
_get_metric_threshold/_get_metric_abs_threshold) to raise ValueError for
BENCH_INFERENCE_METRICS; add threshold tuples for
PerfMetricType.PER_USER_OUTPUT_THROUGHPUT and
PerfMetricType.PER_GPU_OUTPUT_THROUGHPUT (similar to
TOTAL_OUTPUT_THROUGHPUT/TOTAL_TOKEN_THROUGHPUT entries) so the tests can look up
thresholds without failing. Ensure you update the same mapping that currently
contains PerfMetricType.TOTAL_OUTPUT_THROUGHPUT and
PerfMetricType.TOTAL_TOKEN_THROUGHPUT.
---
Outside diff comments:
In `@tests/integration/defs/perf/test_perf.py`:
- Line 1: Update the SPDX header year in the file's top comment by changing the
copyright range end from 2025 to 2026; specifically modify the SPDX line (the
header comment starting with "# SPDX-FileCopyrightText") in
tests/integration/defs/perf/test_perf.py so it reads 2022-2026.
🪄 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: a713544e-9da1-409f-91d3-9e055e4c53fc
⛔ Files ignored due to path filters (2)
tests/integration/defs/perf/base_perf.csvis excluded by!**/*.csvtests/integration/defs/perf/base_perf_pytorch.csvis excluded by!**/*.csv
📒 Files selected for processing (3)
tests/integration/defs/perf/README_release_test.mdtests/integration/defs/perf/test_perf.pytests/integration/defs/perf/utils.py
|
PR_Github #48565 [ skip ] triggered by Bot. Commit: |
|
PR_Github #48565 [ skip ] completed with state |
Signed-off-by: Ruodi Lu <ruodil@users.noreply.github.com>
…rics BENCH_INFERENCE_METRICS collects PER_USER_OUTPUT_THROUGHPUT and PER_GPU_OUTPUT_THROUGHPUT, but PERF_METRIC_THRESHOLD had no entries for them, causing _get_metric_threshold/_get_metric_abs_threshold to raise ValueError before any bench perf command runs. Add (-0.1, 10) entries matching the other throughput metrics. Signed-off-by: Ruodi Lu <ruodil@users.noreply.github.com>
97c1ed2 to
33a3bfb
Compare
|
/bot skip --comment "skip test as just adding metrics" |
|
PR_Github #48821 [ skip ] triggered by Bot. Commit: |
|
PR_Github #48821 [ skip ] completed with state |
Signed-off-by: Ruodi Lu <ruodil@users.noreply.github.com> Co-authored-by: Ruodi Lu <ruodil@users.noreply.github.com>
Summary by CodeRabbit
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.