Skip to content

Conversation

@greg-kwasniewski1
Copy link
Collaborator

@greg-kwasniewski1 greg-kwasniewski1 commented Nov 13, 2025

Tested on the autodeploy dashboard against default setting (heuristics), factory sharding caused no errors or degradation.

Pipeline runs:
with factory sharding:
https://gitlab-master.nvidia.com/ftp/infra/autodeploy-dashboard/-/pipelines/38412013
reference (default):
https://gitlab-master.nvidia.com/ftp/infra/autodeploy-dashboard/-/pipelines/38412033

Summary by CodeRabbit

  • Chores
    • Expanded sharding detection sources to improve model deployment optimization capabilities.

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.

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.

Signed-off-by: greg-kwasniewski1 <213329731+greg-kwasniewski1@users.noreply.github.com>
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 13, 2025

📝 Walkthrough

Walkthrough

A configuration parameter in the default TensorRT-LLM auto-deployment config was updated to expand the sources used for sharding detection. The sharding_source for the detect_sharding transform now includes both factory and heuristic methods instead of only heuristic.

Changes

Cohort / File(s) Change Summary
Configuration update
tensorrt_llm/_torch/auto_deploy/config/default.yaml
Modified transforms.detect_sharding.sharding_source to include 'factory' in addition to the existing 'heuristic' source for sharding detection

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description lacks required template sections including a proper title format, filled-in Description and Test Coverage sections, and incomplete PR Checklist. Add a properly formatted PR title following [type] format, fill in the Description section explaining the change and rationale, and list specific test coverage details in Test Coverage section.
✅ Passed checks (2 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check ✅ Passed The title 'Factory sharding as default' directly and accurately summarizes the main change: enabling factory sharding as a default option in the configuration.
✨ 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.

@greg-kwasniewski1
Copy link
Collaborator Author

/bot run

@greg-kwasniewski1 greg-kwasniewski1 moved this from Backlog to In review in AutoDeploy Board Nov 13, 2025
@lucaslie lucaslie linked an issue Nov 13, 2025 that may be closed by this pull request
1 task
@tensorrt-cicd
Copy link
Collaborator

PR_Github #24489 [ run ] triggered by Bot. Commit: 38a9cd9

@lucaslie lucaslie changed the title [TRTLLM-9137][feat] Factory sharding as default [#9137][feat] Factory sharding as default Nov 13, 2025
@tensorrt-cicd
Copy link
Collaborator

PR_Github #24489 [ run ] completed with state SUCCESS. Commit: 38a9cd9
/LLM/main/L0_MergeRequest_PR pipeline #18483 completed with status: 'FAILURE'

@greg-kwasniewski1
Copy link
Collaborator Author

/bot run

@greg-kwasniewski1
Copy link
Collaborator Author

/bot run --reuse-test

@tensorrt-cicd
Copy link
Collaborator

PR_Github #24588 [ run ] triggered by Bot. Commit: 38a9cd9

@tensorrt-cicd
Copy link
Collaborator

PR_Github #24589 [ run ] triggered by Bot. Commit: 38a9cd9

@tensorrt-cicd
Copy link
Collaborator

PR_Github #24588 [ run ] completed with state ABORTED. Commit: 38a9cd9

@tensorrt-cicd
Copy link
Collaborator

PR_Github #24589 [ run ] completed with state SUCCESS. Commit: 38a9cd9
/LLM/main/L0_MergeRequest_PR pipeline #18560 completed with status: 'FAILURE'

@greg-kwasniewski1
Copy link
Collaborator Author

/bot run --reuse-test

@tensorrt-cicd
Copy link
Collaborator

PR_Github #24606 [ run ] triggered by Bot. Commit: 38a9cd9

@tensorrt-cicd
Copy link
Collaborator

PR_Github #24606 [ run ] completed with state SUCCESS. Commit: 38a9cd9
/LLM/main/L0_MergeRequest_PR pipeline #18573 completed with status: 'SUCCESS'

@lucaslie lucaslie merged commit 92f86a5 into NVIDIA:main Nov 19, 2025
9 of 11 checks passed
@github-project-automation github-project-automation bot moved this from In review to Done in AutoDeploy Board Nov 19, 2025
lkomali pushed a commit to lkomali/TensorRT-LLM that referenced this pull request Nov 19, 2025
Signed-off-by: greg-kwasniewski1 <213329731+greg-kwasniewski1@users.noreply.github.com>
Signed-off-by: lkomali <lkomali@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AutoDeploy <NV> AutoDeploy Backend

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

[Feature][AutoDeploy]: Factory sharding as default

4 participants