mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[GH-ISSUE #164] Is internode api necessary in low_latency mode with a single 8*H200 node? #143
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#143
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 @Yi-sir on GitHub (May 14, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/164
I deployed DeepSeek-R1 using DeepEP on an 8×H200 server. Due to incompatibility between the 'normal' mode interface and CUDA Graph(https://github.com/sgl-project/sglang/issues/6218), I had to use 'low_latency' mode. However, the 'low_latency' mode appears to utilize internode communication interfaces, which rely on an InfiniBand (IB) environment. Currently, our machine’s IB environment is not yet ready.
For this single-machine deployment with 'low_latency' mode, is the IB environment (or specifically, the internode interfaces) still mandatory?
Thank you!
@LyricZhao commented on GitHub (May 14, 2025):
Yes, the local node transfer will also use RDMA.
For NVLink impl, we currently don't have time to do. You can refer to the PPLX kernels, their kernels support that: https://github.com/ppl-ai/pplx-kernels.
@Yi-sir commented on GitHub (May 14, 2025):
thank you