Skip to content

[#10607][feat] added AutoDeploy serving perf test with Super test#12287

Merged
MrGeva merged 6 commits intoNVIDIA:mainfrom
nv-auto-deploy:eg/super_perf_test
Mar 19, 2026
Merged

[#10607][feat] added AutoDeploy serving perf test with Super test#12287
MrGeva merged 6 commits intoNVIDIA:mainfrom
nv-auto-deploy:eg/super_perf_test

Conversation

@MrGeva
Copy link
Collaborator

@MrGeva MrGeva commented Mar 17, 2026

Summary by CodeRabbit

Release Notes

  • Tests
    • Added new model variant support to the test framework for expanded model coverage
    • Enhanced performance testing infrastructure with configurable serving backend support for environment flexibility
    • Implemented configuration merging capabilities to combine embedded and external API configurations for greater test flexibility
    • Extended performance sanity test suite with dedicated multi-GPU scenarios to validate performance behavior across different hardware configurations

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)

  • 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.

@MrGeva MrGeva requested a review from a team as a code owner March 17, 2026 15:42
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 17, 2026

📝 Walkthrough

Walkthrough

Extended ServerConfig class with two new configurable attributes (backend and extra_llm_api_config_path) to support dynamic backend selection and external LLM API configuration merging. Added model path mapping for "super_nvfp4" and introduced a new GB200 multi-GPU post-merge test configuration.

Changes

Cohort / File(s) Summary
ServerConfig Attributes & Methods
tests/integration/defs/perf/test_perf_sanity.py
Added backend and extra_llm_api_config_path public attributes to ServerConfig. Modified to_cmd() to use self.backend instead of hardcoded value. Updated to_db_data() to include backend field. Enhanced generate_extra_llm_api_config() to merge external config from extra_llm_api_config_path with in-YAML config, prioritizing in-YAML data. Added "super_nvfp4" model path mapping.
Performance Test Configuration
tests/integration/test_lists/test-db/l0_gb200_multi_gpus_perf_sanity.yml
Added new post_merge test block for GB200 multi-GPU systems (8 GPU, aarch64 CPU, ubuntu linux) with pytorch backend, executing perf sanity test with 120s timeout.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 75.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check ⚠️ Warning The PR description contains only the template structure with all content sections left blank; no actual description, test coverage details, or implementation specifics are provided. Fill in the Description section explaining what was added and why, detail the Test Coverage section with relevant tests, and complete the PR Checklist to confirm all items have been addressed.
✅ Passed checks (1 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically identifies the main change: adding an AutoDeploy serving performance test with a Super model variant.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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_sanity.py (1)

1-1: ⚠️ Potential issue | 🟠 Major

Update the copyright header year to include 2026.

This file has meaningful modifications in this PR, so the latest year in the NVIDIA Apache-2.0 header should be updated.

As per coding guidelines: **/*.{cpp,h,cu,cuh,hpp,py}: All TensorRT-LLM source files should contain an NVIDIA copyright header with the year of the latest meaningful modification.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@tests/integration/defs/perf/test_perf_sanity.py` at line 1, Update the SPDX
copyright header at the top of the file (the existing SPDX-FileCopyrightText
header line) to include 2026 as the latest year; specifically modify the header
string in tests/integration/defs/perf/test_perf_sanity.py so the year range
reads 2022-2026.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@tests/integration/defs/perf/test_perf_sanity.py`:
- Line 332: ServerConfig.to_match_keys() is missing the persisted
s_serving_backend, causing baselines to mix across serving backends; update the
to_match_keys method to include s_serving_backend in the returned match-key
tuple or dict alongside the existing keys so comparisons account for serving
backend differences and ensure unique matching by backend (refer to the
ServerConfig.to_match_keys function and the s_serving_backend field).

---

Outside diff comments:
In `@tests/integration/defs/perf/test_perf_sanity.py`:
- Line 1: Update the SPDX copyright header at the top of the file (the existing
SPDX-FileCopyrightText header line) to include 2026 as the latest year;
specifically modify the header string in
tests/integration/defs/perf/test_perf_sanity.py so the year range reads
2022-2026.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: b76c9e91-e666-4f97-b058-33f7fece6d66

📥 Commits

Reviewing files that changed from the base of the PR and between bad4c98 and b55711c.

📒 Files selected for processing (2)
  • tests/integration/defs/perf/test_perf_sanity.py
  • tests/integration/test_lists/test-db/l0_gb200_multi_gpus_perf_sanity.yml

@MrGeva
Copy link
Collaborator Author

MrGeva commented Mar 18, 2026

/bot run --stage "GB200-4_GPUs-PyTorch-PerfSanity-1"

1 similar comment
@MrGeva
Copy link
Collaborator Author

MrGeva commented Mar 18, 2026

/bot run --stage "GB200-4_GPUs-PyTorch-PerfSanity-1"

@MrGeva
Copy link
Collaborator Author

MrGeva commented Mar 18, 2026

/bot run --help

@MrGeva
Copy link
Collaborator Author

MrGeva commented Mar 18, 2026

/bot help

@github-actions
Copy link

GitHub Bot Help

/bot [-h] ['run', 'kill', 'skip', 'reuse-pipeline'] ...

Provide a user friendly way for developers to interact with a Jenkins server.

Run /bot [-h|--help] to print this help message.

See details below for each supported subcommand.

Details

run [--reuse-test (optional)pipeline-id --disable-fail-fast --skip-test --stage-list "A10-PyTorch-1, xxx" --gpu-type "A30, H100_PCIe" --test-backend "pytorch, cpp" --add-multi-gpu-test --only-multi-gpu-test --disable-multi-gpu-test --post-merge --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx" --detailed-log --debug(experimental) --high-priority]

Launch build/test pipelines. All previously running jobs will be killed.

--reuse-test (optional)pipeline-id (OPTIONAL) : Allow the new pipeline to reuse build artifacts and skip successful test stages from a specified pipeline or the last pipeline if no pipeline-id is indicated. If the Git commit ID has changed, this option will be always ignored. The DEFAULT behavior of the bot is to reuse build artifacts and successful test results from the last pipeline.

--disable-reuse-test (OPTIONAL) : Explicitly prevent the pipeline from reusing build artifacts and skipping successful test stages from a previous pipeline. Ensure that all builds and tests are run regardless of previous successes.

--disable-fail-fast (OPTIONAL) : Disable fail fast on build/tests/infra failures.

--skip-test (OPTIONAL) : Skip all test stages, but still run build stages, package stages and sanity check stages. Note: Does NOT update GitHub check status.

--stage-list "A10-PyTorch-1, xxx" (OPTIONAL) : Only run the specified test stages. Examples: "A10-PyTorch-1, xxx". Note: Does NOT update GitHub check status.

--gpu-type "A30, H100_PCIe" (OPTIONAL) : Only run the test stages on the specified GPU types. Examples: "A30, H100_PCIe". Note: Does NOT update GitHub check status.

--test-backend "pytorch, cpp" (OPTIONAL) : Skip test stages which don't match the specified backends. Only support [pytorch, cpp, tensorrt, triton]. Examples: "pytorch, cpp" (does not run test stages with tensorrt or triton backend). Note: Does NOT update GitHub pipeline status.

--only-multi-gpu-test (OPTIONAL) : Only run the multi-GPU tests. Note: Does NOT update GitHub check status.

--disable-multi-gpu-test (OPTIONAL) : Disable the multi-GPU tests. Note: Does NOT update GitHub check status.

--add-multi-gpu-test (OPTIONAL) : Force run the multi-GPU tests in addition to running L0 pre-merge pipeline.

--post-merge (OPTIONAL) : Run the L0 post-merge pipeline instead of the ordinary L0 pre-merge pipeline.

--extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx" (OPTIONAL) : Run the ordinary L0 pre-merge pipeline and specified test stages. Examples: --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx".

--detailed-log (OPTIONAL) : Enable flushing out all logs to the Jenkins console. This will significantly increase the log volume and may slow down the job.

--debug (OPTIONAL) : Experimental feature. Enable access to the CI container for debugging purpose. Note: Specify exactly one stage in the stage-list parameter to access the appropriate container environment. Note: Does NOT update GitHub check status.

--high-priority (OPTIONAL) : Run the pipeline with high priority. This option is restricted to authorized users only and will route the job to a high-priority queue.

kill

kill

Kill all running builds associated with pull request.

skip

skip --comment COMMENT

Skip testing for latest commit on pull request. --comment "Reason for skipping build/test" is required. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.

reuse-pipeline

reuse-pipeline

Reuse a previous pipeline to validate current commit. This action will also kill all currently running builds associated with the pull request. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.

@MrGeva
Copy link
Collaborator Author

MrGeva commented Mar 18, 2026

/bot run --stage-list "GB200-4_GPUs-PyTorch-PerfSanity-1"

@tensorrt-cicd
Copy link
Collaborator

PR_Github #39396 [ run ] triggered by Bot. Commit: 745e8f2 Link to invocation

@tensorrt-cicd
Copy link
Collaborator

PR_Github #39398 Bot args parsing error: usage: /bot [-h]
{run,kill,skip,submit,reviewers,reuse-pipeline,reuse-review} ...
/bot: error: unrecognized arguments: --help

Link to invocation

@tensorrt-cicd
Copy link
Collaborator

PR_Github #39399 [ run ] triggered by Bot. Commit: 745e8f2 Link to invocation

@tensorrt-cicd
Copy link
Collaborator

PR_Github #39396 [ run ] completed with state ABORTED. Commit: 745e8f2

Link to invocation

@tensorrt-cicd
Copy link
Collaborator

PR_Github #39399 [ run ] completed with state FAILURE. Commit: 745e8f2
/LLM/main/L0_MergeRequest_PR pipeline #30632 (Partly Tested) completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

Link to invocation

@MrGeva
Copy link
Collaborator Author

MrGeva commented Mar 18, 2026

/bot run --stage-list "GB200-4_GPUs-PyTorch-PerfSanity-1"

@tensorrt-cicd
Copy link
Collaborator

PR_Github #39442 [ run ] triggered by Bot. Commit: 745e8f2 Link to invocation

@tensorrt-cicd
Copy link
Collaborator

PR_Github #39442 [ run ] completed with state SUCCESS. Commit: 745e8f2
/LLM/main/L0_MergeRequest_PR pipeline #30669 (Partly Tested) completed with status: 'SUCCESS'

CI Report

Link to invocation

@MrGeva
Copy link
Collaborator Author

MrGeva commented Mar 18, 2026

/bot run --stage-list "GB200-4_GPUs-PyTorch-PerfSanity-1"

@tensorrt-cicd
Copy link
Collaborator

PR_Github #39472 [ run ] triggered by Bot. Commit: 7e04acb Link to invocation

@tensorrt-cicd
Copy link
Collaborator

PR_Github #39472 [ run ] completed with state SUCCESS. Commit: 7e04acb
/LLM/main/L0_MergeRequest_PR pipeline #30697 (Partly Tested) completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

Link to invocation

@MrGeva
Copy link
Collaborator Author

MrGeva commented Mar 18, 2026

/bot run --stage-list "GB200-4_GPUs-PyTorch-PerfSanity-1"

@tensorrt-cicd
Copy link
Collaborator

PR_Github #39504 [ run ] triggered by Bot. Commit: 3f04545 Link to invocation

@tensorrt-cicd
Copy link
Collaborator

PR_Github #39504 [ run ] completed with state SUCCESS. Commit: 3f04545
/LLM/main/L0_MergeRequest_PR pipeline #30725 (Partly Tested) completed with status: 'SUCCESS'

CI Report

Link to invocation

@MrGeva
Copy link
Collaborator Author

MrGeva commented Mar 19, 2026

/bot run --stage-list "GB200-4_GPUs-PyTorch-PerfSanity-1"

@tensorrt-cicd
Copy link
Collaborator

PR_Github #39551 [ run ] triggered by Bot. Commit: 3f04545 Link to invocation

@tensorrt-cicd
Copy link
Collaborator

PR_Github #39551 [ run ] completed with state FAILURE. Commit: 3f04545
/LLM/main/L0_MergeRequest_PR pipeline #30770 (Partly Tested) completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

Link to invocation

@MrGeva MrGeva requested a review from chenfeiz0326 March 19, 2026 07:45
@MrGeva
Copy link
Collaborator Author

MrGeva commented Mar 19, 2026

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #39568 [ run ] triggered by Bot. Commit: 096fd0e Link to invocation

MrGeva added 6 commits March 19, 2026 02:53
Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
@MrGeva MrGeva force-pushed the eg/super_perf_test branch from 096fd0e to 621aece Compare March 19, 2026 10:07
@MrGeva
Copy link
Collaborator Author

MrGeva commented Mar 19, 2026

/bot run

@MrGeva MrGeva enabled auto-merge (squash) March 19, 2026 10:16
@tensorrt-cicd
Copy link
Collaborator

PR_Github #39587 [ run ] triggered by Bot. Commit: 621aece Link to invocation

@tensorrt-cicd
Copy link
Collaborator

PR_Github #39587 [ run ] completed with state SUCCESS. Commit: 621aece
/LLM/main/L0_MergeRequest_PR pipeline #30800 completed with status: 'SUCCESS'

CI Report

Link to invocation

@MrGeva MrGeva merged commit c7cb576 into NVIDIA:main Mar 19, 2026
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants