mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[GH-ISSUE #101] Why not DeepSeek-V3 choose EP128*PP16 during pretraining #91
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepEP#91
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sneaxiy on GitHub (Mar 31, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/101
Compared to EP64 * PP16 * ZeRO-Stage-1 2, EP128 * PP16 does not need the ZeRO communication of expert parameters. If the communication performance between EP64 and EP128 is almost the same, EP128 * PP16 may be better than EP64 * PP16 * ZeRO-Stage-1 2. Why not DeepSeek-V3 choose EP128*PP16 during pretraining? Is it because the communication performance between EP64 and EP128 differ a lot?
@LyricZhao commented on GitHub (Apr 1, 2025):
The gate divides experts into 8 groups and selects 3 groups, so EP64 (8 nodes) is a must. Or to say, the EP number and gate is co-designed.
And the cost of ZeRO is not to much.
@sneaxiy commented on GitHub (Apr 1, 2025):
Do you mean the gate selects experts on 3 nodes atmost? If we use EP128 and the gate selects 6 nodes atmost, what would be the performance in this case?
@LyricZhao commented on GitHub (Apr 1, 2025):
The RDMA communication volume will be doubled, so the performance is 2x worse.
@sneaxiy commented on GitHub (Apr 1, 2025):
Thanks a lot.