[GH-ISSUE #702] DeepSeek官方聊天的周期性“服务器繁忙” #574

Closed
opened 2026-10-26 21:23:23 +00:00 by bsakaguchi · 6 comments
Owner

Originally created by @DracheTek on GitHub (Jul 1, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-R1/issues/702

北京时间15:00到18:00这段时间,deepseek官方聊天功能总会出现服务器繁忙,R1尤其严重,V3稍好一点。比起为什么会繁忙,我更在意为什么是这个时间繁忙。

Originally created by @DracheTek on GitHub (Jul 1, 2025). Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-R1/issues/702 北京时间15:00到18:00这段时间,deepseek官方聊天功能总会出现服务器繁忙,R1尤其严重,V3稍好一点。比起为什么会繁忙,我更在意为什么是这个时间繁忙。
bsakaguchi 2026-10-26 21:23:23 +00:00
Author
Owner

@Evi233 commented on GitHub (Jul 1, 2025):

It's just a speed limit, you'll find it much better if you start a new chat

<!-- gh-comment-id:3024577866 --> @Evi233 commented on GitHub (Jul 1, 2025): It's just a speed limit, you'll find it much better if you start a new chat
Author
Owner

@DracheTek commented on GitHub (Jul 7, 2025):

I somehow know and understand that, but I' m now working on a novel project, in many cases I can only send one message and get one reply, and then get spammed with "server busy". the initial input is ~20kb background file and ~1000 chinese char description, and it returns with ~10k chinese chars.

这个我知道,限速可以理解。我现在在搞一个小说项目,很多时候只能发一条消息,然后就“服务器繁忙”。第一条消息是一个20kb文件和1000字左右的故事背景解释,会返回约1万字的小说正文。

if we have a queueing instead of outright reject it would be better.

如果服务器带有某种排队机制,使用体验会好不少。

<!-- gh-comment-id:3043799218 --> @DracheTek commented on GitHub (Jul 7, 2025): I somehow know and understand that, but I' m now working on a novel project, in many cases I can only send one message and get one reply, and then get spammed with "server busy". the initial input is ~20kb background file and ~1000 chinese char description, and it returns with ~10k chinese chars. 这个我知道,限速可以理解。我现在在搞一个小说项目,很多时候只能发一条消息,然后就“服务器繁忙”。第一条消息是一个20kb文件和1000字左右的故事背景解释,会返回约1万字的小说正文。 if we have a queueing instead of outright reject it would be better. 如果服务器带有某种排队机制,使用体验会好不少。
Author
Owner

@github-actions[bot] commented on GitHub (Aug 7, 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!

<!-- gh-comment-id:3161994679 --> @github-actions[bot] commented on GitHub (Aug 7, 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!
Author
Owner

@Mbilse commented on GitHub (Aug 7, 2025):

mee,too

<!-- gh-comment-id:3162206446 --> @Mbilse commented on GitHub (Aug 7, 2025): mee,too
Author
Owner

@github-actions[bot] commented on GitHub (Sep 10, 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!

<!-- gh-comment-id:3272730728 --> @github-actions[bot] commented on GitHub (Sep 10, 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!
Author
Owner

@github-actions[bot] commented on GitHub (Sep 24, 2025):

false

<!-- gh-comment-id:3325952111 --> @github-actions[bot] commented on GitHub (Sep 24, 2025): false
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/DeepSeek-R1#574
No description provided.