fp8 triton moe config.#8036
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #8036 +/- ##
==========================================
Coverage ? 67.66%
==========================================
Files ? 470
Lines ? 66115
Branches ? 10189
==========================================
Hits ? 44740
Misses ? 18523
Partials ? 2852
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
PaddlePaddle-bot
left a comment
There was a problem hiding this comment.
🤖 Paddle-CI-Agent | pr_review |
2026-06-11 00:03:39
📋 Review 摘要
PR 概述:调整 FP8 Triton MoE 在小 token 场景下的 tiling 配置。
变更范围:fastdeploy/model_executor/layers/moe/fused_moe_triton_backend.py
影响面 Tag:[OP] [Quantization] [Optimization]
问题
未发现阻塞性问题。PR 规范问题在下面章节报,不要在这里重复
📝 PR 规范检查
标题缺少官方 Tag,PR 描述仍是模板占位内容,未填写 Motivation、Modifications、Usage or Command、Accuracy Tests 和 Checklist 状态。建议替换为以下内容。
标题建议(可直接复制):
[Optimization] Tune FP8 Triton MoE small-token config
PR 描述建议(点击展开,可直接复制)
## Motivation
Tune the Triton MoE FP8 kernel configuration for small-token workloads to use smaller M/N tiles and adjusted pipeline stages.
## Modifications
- In `fastdeploy/model_executor/layers/moe/fused_moe_triton_backend.py`, refine the `Wfp8Afp8MoEMethod.apply` config when `token_num <= E`:
- `token_num <= 16`: use `BLOCK_SIZE_M=16`, `BLOCK_SIZE_N=64`, `num_stages=4`.
- `token_num <= 32`: use `BLOCK_SIZE_M=32`, `BLOCK_SIZE_N=64`, `num_stages=3`.
- `token_num > 32` and `token_num <= E`: keep `BLOCK_SIZE_M=64`, `BLOCK_SIZE_N=128`, and set `num_stages=3`.
## Usage or Command
N/A
## Accuracy Tests
N/A
## Checklist
- [x] Add at least a tag in the PR title.
- Tag list: [`[FDConfig]`,`[APIServer]`,`[Engine]`, `[Scheduler]`, `[PD Disaggregation]`, `[Executor]`, `[Graph Optimization]`, `[Speculative Decoding]`, `[RL]`, `[Models]`, `[Quantization]`, `[Loader]`, `[OP]`, `[KVCache]`, `[DataProcessor]`, `[BugFix]`, `[Docs]`, `[CI]`, `[Optimization]`, `[Feature]`, `[Benchmark]`, `[Others]`, `[XPU]`, `[HPU]`, `[GCU]`, `[DCU]`, `[Iluvatar]`, `[Metax]`]
- You can add new tags based on the PR content, but the semantics must be clear.
- [ ] Format your code, run `pre-commit` before commit.
- [ ] Add unit tests. Please write the reason in this PR if no unit tests.
- [ ] Provide accuracy results.
- [ ] If the current PR is submitting to the `release` branch, make sure the PR has been submitted to the `develop` branch, then cherry-pick it to the `release` branch with the `[Cherry-Pick]` PR tag.总体评价
本轮按风险优先审查了 FP8 Triton MoE 小 token 配置分支,以及该配置传入 preprocess 和两次 fused MoE GEMM kernel 的调用关系;未确认到会改变路由、shape、scale 或写回语义的阻塞性问题。建议补齐 PR 标题和描述中的规范信息,尤其是性能/精度验证结果或未提供的原因。
CI报告基于以下代码生成(30分钟更新一次): 1 Required任务 : 9/10 通过
2 失败详情🔴 Run FastDeploy Unit Tests and Coverage / run_tests_with_coverage — PR问题(置信度: 高)错误类型: PR问题 | 置信度: 高
关键日志:
修复建议:
关联变更: |
Motivation
Modifications
Usage or Command
Accuracy Tests
Checklist
[FDConfig],[APIServer],[Engine],[Scheduler],[PD Disaggregation],[Executor],[Graph Optimization],[Speculative Decoding],[RL],[Models],[Quantization],[Loader],[OP],[KVCache],[DataProcessor],[BugFix],[Docs],[CI],[Optimization],[Feature],[Benchmark],[Others],[XPU],[HPU],[GCU],[DCU],[Iluvatar],[Metax]]pre-commitbefore commit.releasebranch, make sure the PR has been submitted to thedevelopbranch, then cherry-pick it to thereleasebranch with the[Cherry-Pick]PR tag.