[https://nvbugs/5836830][fix] Fix DeepSeekV3 W4A8 mixed precision quantization for MoE experts - #12149
[https://nvbugs/5836830][fix] Fix DeepSeekV3 W4A8 mixed precision quantization for MoE experts#12149Barry-Delaney wants to merge 3 commits into
Conversation
📝 WalkthroughWalkthroughThe changes implement per-expert and per-module quantization override propagation in DeepSeek-v3 model construction and configurable MoE layers. Quantization configuration resolution is centralized at per-layer and per-expert initialization stages, replacing previous per-call recomputation with dedicated override configuration storage and application logic. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~22 minutes 🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment Tip CodeRabbit can use Trivy to scan for security misconfigurations and secrets in Infrastructure as Code files.Add a .trivyignore file to your project to customize which findings Trivy reports. |
|
/bot run |
|
PR_Github #38699 [ run ] triggered by Bot. Commit: |
litaotju
left a comment
There was a problem hiding this comment.
LGTM — clean fix, good comments. One question: are there any test cases in CI or post-merge that exercise the MIXED_PRECISION path through MoE init (e.g. the W4AFP8 quickstart test from the bug)? Want to make sure this gets regression-covered going forward.
|
PR_Github #38699 [ run ] completed with state
|
|
/bot run |
|
PR_Github #38831 [ run ] triggered by Bot. Commit: |
Thanks on the review @litaotju! It seems the test is only covered in QA, I added one into post-merge in the latest commit. |
|
/bot kill |
|
PR_Github #38832 [ kill ] triggered by Bot. Commit: |
|
PR_Github #38832 [ kill ] completed with state |
|
/bot run |
|
PR_Github #38834 [ run ] triggered by Bot. Commit: |
|
PR_Github #38834 [ run ] completed with state
|
c1f1080 to
b30bd67
Compare
|
/bot run |
|
PR_Github #39677 [ run ] triggered by Bot. Commit: |
|
PR_Github #42317 [ run ] completed with state
|
|
/bot run |
c0d799b to
8343239
Compare
|
/bot run |
|
PR_Github #42498 [ run ] triggered by Bot. Commit: |
|
PR_Github #42498 [ run ] completed with state
|
|
/bot run |
|
PR_Github #43196 [ run ] triggered by Bot. Commit: |
|
PR_Github #43196 [ run ] completed with state |
|
/bot kill |
|
PR_Github #43201 [ kill ] triggered by Bot. Commit: |
|
PR_Github #43201 [ kill ] completed with state |
|
/bot run |
|
PR_Github #43612 [ run ] triggered by Bot. Commit: |
|
PR_Github #43612 [ run ] completed with state
|
|
/bot run |
|
PR_Github #43713 [ run ] triggered by Bot. Commit: |
|
PR_Github #43713 [ run ] completed with state
|
Resolve per-expert quant config (e.g. W4A8_AWQ) from the global MIXED_PRECISION config so that MoE backends receive the correct quantization strategy. Previously the ambiguous MIXED_PRECISION config was passed through, causing assertion failures and incorrect weight loading. For non-MIXED_PRECISION cases (e.g. nvfp4, unquantized MTP layers), pass override_quant_config through as-is since it already encodes the correct exclusions. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Barry Kang <43644113+Barry-Delaney@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Barry Kang <43644113+Barry-Delaney@users.noreply.github.com>
|
/bot run |
|
PR_Github #44944 [ run ] triggered by Bot. Commit: |
Resolve per-expert quant config (e.g. W4A8_AWQ) from the global MIXED_PRECISION config so that MoE backends receive the correct quantization strategy. Previously the ambiguous MIXED_PRECISION config was passed through, causing assertion failures and incorrect weight loading.
Summary by CodeRabbit
Bug Fixes
Refactor