Skip to content

Conversation

rosenrodt
Copy link
Collaborator

@rosenrodt rosenrodt commented Aug 21, 2025

Summary by CodeRabbit

  • New Features

    • Per-layer quantization support for MoE experts, enabling finer-grained control and consistent behavior across related modules.
    • Int4 per-group weight loading now respects layer-specific quant settings.
  • Bug Fixes

    • Guards to prevent ambiguous mixed-precision quantization, reducing runtime errors.
    • More reliable initialization for resolving per-layer quant settings in MoE components.
  • Refactor

    • Centralized quantization-resolution logic across decoder/MoE paths for consistency.

Description

MoE quant mode should be determined by individual layers in the quant_config for DS-R1 MIXED_PRECISION quant_algo.

Test Coverage

No test coverage at this moment.

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.

@rosenrodt rosenrodt requested review from a team as code owners August 21, 2025 09:59
@rosenrodt rosenrodt requested review from hlu1 and symphonylyh August 21, 2025 09:59
Copy link
Contributor

coderabbitai bot commented Aug 21, 2025

📝 Walkthrough

Walkthrough

Adds per-layer expert quantization resolution to Deepseek V3 MoE components: introduces a helper to fetch per-layer expert QuantConfig (with fallback), switches weight-loading decisions to use per-layer quant_mode, and adds an assertion forbidding MIXED_PRECISION during decoder/MoE initialization.

Changes

Cohort / File(s) Summary
MoE per-layer quant config resolution
tensorrt_llm/_torch/models/modeling_deepseekv3.py
Added static helper _get_experts_quant_config(model_config, layer_idx) to return per-layer QuantConfig or fallback; replaced global quant_mode checks with per-layer lookups for int4 per-group weight_loading_mode; imported QuantAlgo and added assertion disallowing MIXED_PRECISION; applied changes in Deepseekv3MoE and DeepseekV3MTP.

Sequence Diagram(s)

sequenceDiagram
  participant App as Model init
  participant Layer as DecoderLayer (MoE)
  participant QC as _get_experts_quant_config
  participant Weights as Weight Loader

  App->>Layer: Initialize layer (layer_idx)
  Layer->>QC: Fetch experts QuantConfig(layer_idx)
  QC-->>Layer: QuantConfig (per-layer or fallback)

  alt QuantConfig.quant_algo == MIXED_PRECISION
    Layer->>Layer: Assert fail (disallow MIXED_PRECISION)
  else
    Layer->>Weights: Determine weight_loading_mode from per-layer quant_mode
    Weights-->>Layer: Load expert weights
  end
Loading
sequenceDiagram
  participant App as MTP init
  participant MTP as DeepseekV3MTP
  participant QC as _get_experts_quant_config
  participant Weights as Weight Loader

  App->>MTP: Initialize MoE experts (layer_idx)
  MTP->>QC: Get experts QuantConfig(layer_idx)
  QC-->>MTP: QuantConfig
  MTP->>Weights: Set weight_loading_mode based on per-layer quant_mode
  Weights-->>MTP: Load expert weights
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

Suggested labels

Community want to contribute

Suggested reviewers

  • hlu1
  • yuxianq
  • byshiue
  • nv-yilinf

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.


📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between cdda63e and efd670a.

📒 Files selected for processing (1)
  • tensorrt_llm/_torch/models/modeling_deepseekv3.py (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • tensorrt_llm/_torch/models/modeling_deepseekv3.py
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Pre-commit Check
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • 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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@rosenrodt
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #16307 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #16307 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #12260 completed with status: 'FAILURE'

@rosenrodt
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #16318 [ run ] triggered by Bot

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: 3

🧹 Nitpick comments (2)
tensorrt_llm/_torch/models/modeling_deepseekv3.py (2)

48-48: Drop QuantAlgo import if the global assert is removed

If you adopt the per-layer NVFP4 resolution and remove the MIXED_PRECISION assert (Lines 649-652), this import becomes unused and may fail lint in CI.

-from tensorrt_llm.quantization.mode import QuantAlgo

461-467: Add minimal unit coverage for W4A8 per-layer resolution

This PR changes the selection of MoEWeightLoadingMode based on per-layer config, but ships without tests. Add a focused test that constructs a ModelConfig with a quant_config_dict entry for model.layers.{i}.mlp.experts set to an int4-per-group mode and asserts that Deepseekv3MoE(..., layer_idx=i) picks W4A8_CUSTOM; also verify the fallback to VANILLA when the entry is absent.

I can draft a minimal test that stubs QuantConfig/QuantMode to assert the mode switch without needing GPU ops. Want me to open a follow-up PR with the test?

Also applies to: 532-538

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 99b382b and 64ab562.

📒 Files selected for processing (1)
  • tensorrt_llm/_torch/models/modeling_deepseekv3.py (4 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
**/*.py

📄 CodeRabbit inference engine (CODING_GUIDELINES.md)

**/*.py: Python code must target Python 3.8+
Python indentation: 4 spaces, no tabs
Maintain module namespace in imports (from package.subpackage import foo; then use foo.SomeClass())
Python file names use snake_case
Python class names use PascalCase
Python functions/methods and local variables use snake_case; variables starting with a number get k_ prefix (e.g., k_99th_percentile)
Global variables use G_ prefixed UPPER_SNAKE_CASE (e.g., G_MY_GLOBAL)
Constants use UPPER_SNAKE_CASE in Python
Avoid shadowing variables from outer scopes in Python
Initialize all externally visible members of a Python class in init
Prefer docstrings for interfaces used outside a file; comments for local code
Use Google-style docstrings for classes and functions (Sphinx-parsable)
Document attributes/variables inline with short docstrings
Avoid reflection when simple alternatives exist (e.g., prefer explicit parameters over dict(**locals()))
In try/except, catch the narrowest exceptions possible
For duck-typing with try/except, keep try body minimal and put logic in else

Files:

  • tensorrt_llm/_torch/models/modeling_deepseekv3.py
**/*.{cpp,cxx,cc,cu,h,hpp,hxx,hh,cuh,py}

📄 CodeRabbit inference engine (CODING_GUIDELINES.md)

Prepend NVIDIA copyright header (current year) to all source files

Files:

  • tensorrt_llm/_torch/models/modeling_deepseekv3.py
🧬 Code graph analysis (1)
tensorrt_llm/_torch/models/modeling_deepseekv3.py (4)
tensorrt_llm/quantization/mode.py (2)
  • QuantAlgo (23-46)
  • is_int4_weight_only_per_group (133-134)
tensorrt_llm/_torch/modules/fused_moe/interface.py (1)
  • MoEWeightLoadingMode (13-19)
tensorrt_llm/models/modeling_utils.py (3)
  • layer_quant_mode (166-170)
  • layer_quant_mode (306-312)
  • quant_algo (547-548)
tensorrt_llm/llmapi/llm_args.py (2)
  • quant_config (2175-2178)
  • quant_config (2181-2182)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Pre-commit Check
🔇 Additional comments (1)
tensorrt_llm/_torch/models/modeling_deepseekv3.py (1)

649-652: No action needed: layer_quant_mode API signatures confirmed

layer_quant_mode exists as a zero-argument cached property (returns a uniform QuantMode) in
tensorrt_llm/models/modeling_utils.py at line 166.
• It also exists as a method accepting a single layer_name argument (for per-layer modes) in
tensorrt_llm/models/modeling_utils.py at line 306.

Since this change neither introduces any new calls to layer_quant_mode nor relies on QuantAlgo.MIXED_PRECISION, the existing API surface remains compatible.

@tensorrt-cicd
Copy link
Collaborator

PR_Github #16318 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #12270 completed with status: 'FAILURE'

@rosenrodt
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #16340 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #16340 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #12282 completed with status: 'FAILURE'

@rosenrodt
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #16381 [ run ] triggered by Bot

@rosenrodt
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #16398 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #16381 [ run ] completed with state ABORTED

@tensorrt-cicd
Copy link
Collaborator

PR_Github #16398 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #12323 completed with status: 'FAILURE'

@rosenrodt
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #16425 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #16425 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #12343 completed with status: 'FAILURE'

@byshiue
Copy link
Collaborator

byshiue commented Sep 5, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #17726 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #17726 [ run ] completed with state DISABLED
L0 testing is limited to prioritized users. User byshiue is not in the prioritized list. L0 testing cannot be triggered.

@byshiue
Copy link
Collaborator

byshiue commented Sep 5, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #17778 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

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

@byshiue byshiue merged commit 12c66f7 into NVIDIA:main Sep 6, 2025
4 checks passed
Wong4j pushed a commit to Wong4j/TensorRT-LLM that referenced this pull request Sep 20, 2025
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.

3 participants