mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[GH-ISSUE #590] Poor HybridEP performance on dual-node 16x B300 GPUs - IB bandwidth significantly lower than expected #361
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#361
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 @sssssakuraaaaa on GitHub (Mar 12, 2026).
Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/590
I'm experiencing poor performance with HybridEP on a dual-node setup with 16 B300 GPUs (8 GPUs per node). The Roce bandwidth is significantly lower than expected, causing performance degradation in cross-node communication.
Environment
Hardware: Dual-node setup, 16x NVIDIA B300 GPUs (8 GPUs per node)
Network: RoCE + NVLink (NVL)
Test Configuration:
Processes per node: 8
Token size: 4096
Local experts: 8
Hidden size: 7168
Node num: 2
Nranks: 16
Performance Data
BF16 performance
FP8 performance
The HybridEP performance for EP 16 is much worse than DeepEP。During HybridEP running, there is no log except performance log。 how can I debug this issue ?
@alpha-baby commented on GitHub (Apr 17, 2026):
EP 16 hybrid-ep performance
@Autumn1998 Could you please advise if the performance from my testing meets expectations? I tuned the configuration parameters, and this set currently appears to deliver the best performance.
env :
my machine
B300 + CX8 (800Gb/s)
hybrid-ep version:
@Autumn1998 commented on GitHub (Apr 28, 2026):
The original hybrid EP implementation was not adapted for dual-port devices like CX8, so there will be performance issues. I believe your configuration is fine — this is purely a design issue with HEP. For this reason we introduced the nixl backend. We will fix these issues as soon as possible, and we sincerely apologize for any inconvenience caused