mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[PR #277] Allow using few SMs for low-latency mode #498
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#498
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?
📋 Pull Request Information
Original PR: https://github.com/deepseek-ai/DeepEP/pull/277
Author: @fzyzcjy
Created: 7/3/2025
Status: 🔄 Open
Base:
main← Head:feat/few_sm_deepep📝 Commits (1)
8d1c641more📊 Changes
1 file changed (+6 additions, -2 deletions)
View changed files
📝
csrc/kernels/internode_ll.cu(+6 -2)📄 Description
The code diff is surely not for merging, but for demonstration how the experiments below are done. If anyone is interested / this direction looks acceptable to be merged, I am happy to polish and further work on the code!
The code and experiment data are extracted from old experiments for my previous https://github.com/deepseek-ai/DeepEP/pull/249.
Figure 1: num-sm vs performance
As can be seen, when using 9 warpgroup - ie few SMs, the performance only slightly slow down. Thus this makes a simple overlapping between this and computation feasible.
For dispatch we may need to do extra work though, since the warp specialization may be suboptimal when there are few SMs.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.