Skip to content

[None][chore] added AutoDeploy nano_v3_multi_device.yaml - #10845

Merged
MrGeva merged 4 commits into
NVIDIA:mainfrom
nv-auto-deploy:eg/nano_scale
Feb 12, 2026
Merged

[None][chore] added AutoDeploy nano_v3_multi_device.yaml#10845
MrGeva merged 4 commits into
NVIDIA:mainfrom
nv-auto-deploy:eg/nano_scale

Conversation

@MrGeva

@MrGeva MrGeva commented Jan 20, 2026

Copy link
Copy Markdown
Collaborator

Added a yaml for nano v3 tp>1 configuration that is copied from nano_v3.yaml and enabled TRTLLMSampler and disables moe multi stream due to #10608

Summary by CodeRabbit

  • Documentation
    • Added a new example YAML configuration file for nano_v3_scale model deployment using TRTLLM runtime. This comprehensive configuration demonstrates advanced optimization techniques including automatic model sharding strategies, memory optimization tuning, specialized attention backends, intelligent caching approaches, and MoE feature support for delivering optimized inference performance.

✏️ Tip: You can customize this high-level summary in your review settings.

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

/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)]

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.

For guidance on mapping tests to stage names, see docs/source/reference/ci-overview.md
and the scripts/test_to_stage_mapping.py helper.

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
MrGeva requested review from a team as code owners January 20, 2026 13:10
@coderabbitai

coderabbitai Bot commented Jan 20, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

This pull request adds a new YAML configuration file for nano_v3_scale deployment. The configuration specifies TRTLLM runtime settings with advanced features including chunked prefill, mamba SSM sharding, MoE (disabled), and tensor parallelism strategies across various projection layers.

Changes

Cohort / File(s) Summary
Configuration File Addition
examples/auto_deploy/nano_v3_scale.yaml
New TRTLLM inference configuration with runtime backend (torch-cudagraph), attention (flashinfer), batch size limits (128 max_batch_size), sequence length support (4096 max_seq_len), manual tensor parallelism plan for mamba SSM (in_proj, out_proj, q_proj, k_proj, v_proj, o_proj, up_proj, down_proj, fc1_latent_proj, fc2_latent_proj), disabled multi-stream MoE stage, cached SSM attention, and post-load mamba fusion

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 1 | ❌ 2
❌ Failed checks (2 warnings)
Check name Status Explanation Resolution
Description check ⚠️ Warning PR description is incomplete and missing critical required sections from the template including proper title format, detailed description explanation, and test coverage information. Add a properly formatted title following [JIRA/Issue][type] format (e.g., [#10608][feat]), expand the Description section explaining the issue and solution, list relevant test cases in Test Coverage section, and complete the PR Checklist.
Title check ⚠️ Warning The PR title references 'nano_v3_multi_device.yaml' but the actual file added is 'nano_v3_scale.yaml', creating a mismatch between the title and the actual changeset. Update the PR title to '[None][chore] added AutoDeploy nano_v3_scale.yaml' to accurately reflect the file being added.
✅ Passed checks (1 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@MrGeva

MrGeva commented Jan 20, 2026

Copy link
Copy Markdown
Collaborator Author

/bot run

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #32755 [ run ] triggered by Bot. Commit: 692e1bf

Comment thread examples/auto_deploy/nano_v3_multi_device.yaml
Comment thread examples/auto_deploy/nano_v3_scale.yaml Outdated
@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #32755 [ run ] completed with state SUCCESS. Commit: 692e1bf
/LLM/main/L0_MergeRequest_PR pipeline #25352 completed with status: 'SUCCESS'
Pipeline passed with automatic retried tests. Check the rerun report for details.

Comment thread examples/auto_deploy/nano_v3_scale.yaml Outdated
Comment thread examples/auto_deploy/nano_v3_multi_device.yaml
Comment thread examples/auto_deploy/nano_v3_multi_device.yaml
@MrGeva

MrGeva commented Jan 28, 2026

Copy link
Copy Markdown
Collaborator Author

/bot run --extra-stage "DGX_B200-4_GPUs-AutoDeploy-1, DGX_H100-4_GPUs-AutoDeploy-1"

@MrGeva

MrGeva commented Jan 28, 2026

Copy link
Copy Markdown
Collaborator Author

/bot run

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #33886 [ run ] triggered by Bot. Commit: 148dcb2

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #33887 [ run ] triggered by Bot. Commit: 148dcb2

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #33887 [ run ] completed with state SUCCESS. Commit: 148dcb2
/LLM/main/L0_MergeRequest_PR pipeline #26132 completed with status: 'FAILURE'

⚠️ 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

@MrGeva

MrGeva commented Jan 28, 2026

Copy link
Copy Markdown
Collaborator Author

/bot run

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #33892 [ run ] triggered by Bot. Commit: 148dcb2

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #33892 [ run ] completed with state ABORTED. Commit: 148dcb2
LLM/main/L0_MergeRequest_PR #26137 (Blue Ocean) completed with status: ABORTED

@MrGeva

MrGeva commented Jan 29, 2026

Copy link
Copy Markdown
Collaborator Author

/bot run

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #33990 [ run ] triggered by Bot. Commit: 148dcb2

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #33990 [ run ] completed with state SUCCESS. Commit: 148dcb2
/LLM/main/L0_MergeRequest_PR pipeline #26222 completed with status: 'SUCCESS'

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 commented Feb 11, 2026

Copy link
Copy Markdown
Collaborator Author

/bot run

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #35654 [ run ] triggered by Bot. Commit: cd5e116

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #35654 [ run ] completed with state SUCCESS. Commit: cd5e116
/LLM/main/L0_MergeRequest_PR pipeline #27532 completed with status: 'FAILURE'

⚠️ 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

@MrGeva

MrGeva commented Feb 12, 2026

Copy link
Copy Markdown
Collaborator Author

/bot run

@suyoggupta

Copy link
Copy Markdown
Collaborator

why do we need a CI run for this?

@MrGeva

MrGeva commented Feb 12, 2026

Copy link
Copy Markdown
Collaborator Author

we dont. I will bypass ci

@MrGeva

MrGeva commented Feb 12, 2026

Copy link
Copy Markdown
Collaborator Author

/bot skip --comment "This commit adds a yaml file, not used by any test or code, so no risk to CI"

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #35730 [ run ] triggered by Bot. Commit: cd5e116

@MrGeva
MrGeva enabled auto-merge (squash) February 12, 2026 05:46
@MrGeva MrGeva changed the title [None][chore] added AutoDeploy nano_v3_scale.yaml [None][chore] added AutoDeploy nano_v3_multi_device.yaml Feb 12, 2026
@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #35731 [ skip ] triggered by Bot. Commit: cd5e116

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #35731 [ skip ] completed with state SUCCESS. Commit: cd5e116
Skipping testing for commit cd5e116

@MrGeva
MrGeva merged commit 31314b9 into NVIDIA:main Feb 12, 2026
7 checks passed
ekou24 pushed a commit to ekou24/TensorRT-LLM that referenced this pull request Feb 16, 2026
Signed-off-by: Eran Geva <19514940+MrGeva@users.noreply.github.com>
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