mirror of
https://github.com/deepseek-ai/DeepSeek-Coder.git
synced 2026-11-05 00:57:19 +00:00
[GH-ISSUE #34] 6.7B的模型需要多少显存? #26
Labels
No labels
documentation
ENV
pull-request
research question
WIP
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepSeek-Coder#26
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 @askxiaozhang on GitHub (Nov 15, 2023).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-Coder/issues/34
@guoday commented on GitHub (Nov 22, 2023):
如果是fp16的话,大概需要14G~15G的显存
@II-Matto commented on GitHub (Nov 22, 2023):
@guoday Hi, I tried to fine-tune the model in fp16 mode which results in large training loss (>4.0) and NaN eval loss. Turning off the fp16 mode solves the loss problem but the training speed is unbearably slow. It seems that the loss problem is due to the original model training in bf16 mode. How could I fine-tune the model in fp16 mode to obtain normal results, i.e. without the large and NaN loss problem? Great thanks.
@guoday commented on GitHub (Nov 22, 2023):
Do you use apex when you fine-tune the model in fp16?
@II-Matto commented on GitHub (Nov 22, 2023):
@guoday I used the Llama-X for fine-tuning, which is quite similar to the DeepSeek-Coder official fine-tuning script. I have not found any explicit clue that apex is used. Could you give some more specific guidance or links to references?
@askxiaozhang commented on GitHub (Nov 22, 2023):
好的,非常感谢!
@soloice commented on GitHub (Nov 28, 2023):
There's no apex configuration in our released code and we do not use fp16/amp when training our model. If you want to train it with fp16, I guess you'll need to find a training framework that supports amp (Maybe DeepSpeed?)
Closed this issue because the original question has been addressed. Feel free to open another issue if you still have questions.