[GH-ISSUE #123] Why is there no fp8 combine? #109

Closed
opened 2026-10-26 09:54:27 +00:00 by bsakaguchi · 4 comments
Owner

Originally created by @thefacetakt on GitHub (Apr 15, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/123

Hi!

I was wondering if there why is there no fp8 combine method. Did you find it detrimental to training process even when performing intermediate accumulation in fp32?

Originally created by @thefacetakt on GitHub (Apr 15, 2025). Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/123 Hi! I was wondering if there why is there no fp8 combine method. Did you find it detrimental to training process even when performing intermediate accumulation in fp32?
Author
Owner

@qijiaxing commented on GitHub (Apr 16, 2025):

is it because the MoE Grouped GEMM output in bf16?

<!-- gh-comment-id:2808792366 --> @qijiaxing commented on GitHub (Apr 16, 2025): is it because the MoE Grouped GEMM output in bf16?
Author
Owner

@MichaelEk commented on GitHub (Apr 16, 2025):

is it because the MoE Grouped GEMM output in bf16?

BF16 combine communication is more expensive than FP8 quantization/dequantization kernels. Also, it is hard to overlap it during the forward pass.

<!-- gh-comment-id:2809212552 --> @MichaelEk commented on GitHub (Apr 16, 2025): > is it because the MoE Grouped GEMM output in bf16? BF16 combine communication is more expensive than FP8 quantization/dequantization kernels. Also, it is hard to overlap it during the forward pass.
Author
Owner

@LyricZhao commented on GitHub (May 14, 2025):

Sorry for my late reply, please see comments in #161.

<!-- gh-comment-id:2879488876 --> @LyricZhao commented on GitHub (May 14, 2025): Sorry for my late reply, please see comments in #161.
Author
Owner

@thefacetakt commented on GitHub (May 14, 2025):

@LyricZhao, thanks for the detailed reply!

<!-- gh-comment-id:2879729561 --> @thefacetakt commented on GitHub (May 14, 2025): @LyricZhao, thanks for the detailed reply!
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/DeepEP#109
No description provided.