mirror of
https://github.com/deepseek-ai/DeepSeek-R1.git
synced 2026-11-05 00:47:42 +00:00
[GH-ISSUE #460] Hardware and Configuration Guidelines for DeepSeek-R1 "Full Version" Deployment #369
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepSeek-R1#369
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 @Zephyrsailor on GitHub (Feb 20, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-R1/issues/460
Description:
We are planning to deploy the DeepSeek-R1 "full version" in a production environment and would like to confirm certain hardware and configuration requirements to ensure smooth deployment. Below are the key questions we have regarding the hardware configuration:
1. Model Precision:
2. Hardware Configuration:
3. Other Configurations:
Thank you for providing the detailed technical insights and configuration advice. If there are any further documents or configuration guidelines, please let us know.
@pp5ee commented on GitHub (Feb 27, 2025):
I am just curious about the speed of multi-GPU communication when it is doing the inference, we have an 18xGPU hardware solution (single rig, one motherboard) with PCIE4 or PCIE5, and we are about to test it, and once I have the result I can share it to you. And by the way, many people modify the vram of 4090 0r 3090 from 24g to 48G or even 90g(?) to fit the requirement of large param model inference, the key ,I think, is the communication speed.
@github-actions[bot] commented on GitHub (Apr 23, 2025):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!
@github-actions[bot] commented on GitHub (May 27, 2025):
false