mirror of
https://github.com/deepseek-ai/DeepSeek-MoE.git
synced 2026-11-05 00:57:43 +00:00
[GH-ISSUE #5] GPU utils is low compared with dense model #6
Labels
No labels
pull-request
WIP
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepSeek-MoE#6
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 @charliedream1 on GitHub (Jan 12, 2024).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-MoE/issues/5
training time is longer than 14B model. GPU utils is low, it always drop to 0 and raise up again to 100%.
@zwd003 commented on GitHub (Jan 12, 2024):
currently,this code has not been extensively optimized for efficient training(e.g. fused moe kernel or expert parallelism). When resources are sufficient, it is recommended that you use zero1 to reduce communication overhead.
@charliedream1 commented on GitHub (Jan 12, 2024):
thanks for reply. Hopefully, these optimization will be added soon
@charliedream1 commented on GitHub (Jan 14, 2024):
So what would be the reason of much slower by equally compared with 14B model without optimizations? Activation params is only 2.7B,however, training is much slower than 14B model, even slower than 20B model. Is that because too many experts calculated in a pipeline but not parallel?
---Original---
From: "wangding @.>
Date: Fri, Jan 12, 2024 15:08 PM
To: @.>;
Cc: "Optimus @.@.>;
Subject: Re: [deepseek-ai/DeepSeek-MoE] GPU utils is low compared with densemodel (Issue #5)
currently,this code has not been extensively optimized for efficient training(e.g. fused moe kernel or expert parallelism). When resources are sufficient, it is recommended that you use zero1 to reduce communication overhead.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
@soloice commented on GitHub (Feb 4, 2024):
too many fragmented matmul and network communication