Colibreh @bnew explains difference between ChatGPT and Chinese AI Deepseek
- Thread starter Seoul Gleou
- Start date
1/14
@_lewtun
I'm running a shyt-ton of GRPO experiments on DeepSeek's distilled models with the LIMO dataset and it really works well
!
Depending on the hyperparameters, I'm able to get ~10 point boost on AIME24 and GPQA, with ~3 point boost on MATH-500 (likely saturated).
Link with more details in post below
2/14
@_lewtun
I'll be using this discussion tab to track my progress - chime in there if you have other ideas to test!
open-r1/README · [Experiment] Applying GRPO to DeepSeek-R1-Distill-Qwen-1.5B with LIMO
3/14
@Teknium1
Is there a standardized way to run aime?
4/14
@_lewtun
We use a custom lighteval task in open-r1 that generates 32k tokens and then applies @HKydlicek's amazing math-verify parser to compare with the ground truth: GitHub - huggingface/open-r1: Fully open reproduction of DeepSeek-R1
5/14
@chewkokwah
Will you test it on the recently released AIME 2025 ?
6/14
@_lewtun
Yes!
7/14
@MaziyarPanahi
awesome work! I tried the 0.5B and 3B, but with the Unsloth code I can go up to Llama 8B.
But today I will switch to Qwen2.5 7B base then eval, then do some distillations (or use what's already out there) and then GRPO then eval.
Which repo/branch are you using for the evals?
8/14
@_lewtun
Cool, excited to see what you get! The evals are running on the main branch of open-r1: GitHub - huggingface/open-r1: Fully open reproduction of DeepSeek-R1
9/14
@IAmEricHedlin
Very cool! I’m curious what kind of gpus you’re using and how many?
10/14
@_lewtun
All experiments running on one node of 8 x H100s
11/14
@bronzeagepapi
Great to see experiments alike, I find 3b to be more stable and representative from a scaling perspective
Is have also been trying 7b+ with unsloth setup
12/14
@_lewtun
Yeah the 1.5B model certainly has some quirks
Are you applying GRPO directly to the base model or first doing distillation and then GRPO?
13/14
@paws4puzzles
Impressive work on LIMO! That 10-point boost on AIME24 and GPQA is stellar. Any tips on hyperparameter tuning?
14/14
@Nuliayuk
I could be wrong, but I think you missed the point of the LIMO paper if you're running GRPO with their dataset.
To post tweets in this format, more info here: https://www.thecoli.com/threads/tips-and-tricks-for-posting-the-coli-megathread.984734/post-52211196
@_lewtun
I'm running a shyt-ton of GRPO experiments on DeepSeek's distilled models with the LIMO dataset and it really works well
!Depending on the hyperparameters, I'm able to get ~10 point boost on AIME24 and GPQA, with ~3 point boost on MATH-500 (likely saturated).
Link with more details in post below
2/14
@_lewtun
I'll be using this discussion tab to track my progress - chime in there if you have other ideas to test!
open-r1/README · [Experiment] Applying GRPO to DeepSeek-R1-Distill-Qwen-1.5B with LIMO
3/14
@Teknium1
Is there a standardized way to run aime?
4/14
@_lewtun
We use a custom lighteval task in open-r1 that generates 32k tokens and then applies @HKydlicek's amazing math-verify parser to compare with the ground truth: GitHub - huggingface/open-r1: Fully open reproduction of DeepSeek-R1
5/14
@chewkokwah
Will you test it on the recently released AIME 2025 ?
6/14
@_lewtun
Yes!
7/14
@MaziyarPanahi
awesome work! I tried the 0.5B and 3B, but with the Unsloth code I can go up to Llama 8B.
But today I will switch to Qwen2.5 7B base then eval, then do some distillations (or use what's already out there) and then GRPO then eval.
Which repo/branch are you using for the evals?
8/14
@_lewtun
Cool, excited to see what you get! The evals are running on the main branch of open-r1: GitHub - huggingface/open-r1: Fully open reproduction of DeepSeek-R1
9/14
@IAmEricHedlin
Very cool! I’m curious what kind of gpus you’re using and how many?
10/14
@_lewtun
All experiments running on one node of 8 x H100s
11/14
@bronzeagepapi
Great to see experiments alike, I find 3b to be more stable and representative from a scaling perspective
Is have also been trying 7b+ with unsloth setup
12/14
@_lewtun
Yeah the 1.5B model certainly has some quirks
Are you applying GRPO directly to the base model or first doing distillation and then GRPO?13/14
@paws4puzzles
Impressive work on LIMO! That 10-point boost on AIME24 and GPQA is stellar. Any tips on hyperparameter tuning?
14/14
@Nuliayuk
I could be wrong, but I think you missed the point of the LIMO paper if you're running GRPO with their dataset.
To post tweets in this format, more info here: https://www.thecoli.com/threads/tips-and-tricks-for-posting-the-coli-megathread.984734/post-52211196
Loading…
archive.is
Hey Reddit! 
I’m an independent developer who, like many of you, got tired of seeing DeepSeek constantly throwing the dreaded "Server is busy. Please try again later." error.
It’s frustrating, right? Having to manually click the Regenerate button over and over again is a waste of time and focus. So, I decided to do something about it!
I’m excited to share DeepSeek Server Busy - Chrome Web Store, a Chrome extension that automates the retry process for you. No more manual clicking, no more frustration. Just sit back and let the extension handle it and then return back to the tab in awhile!
https://i.redd.it/cunxfu7i4xhe1.png
Key Features
Automatic Retries
When DeepSeek says the server is busy, the extension automatically retries the request for you. No more manual clicking!
It waits for a random delay (configurable by you) before retrying, so you don’t overload the server.
Customizable Delays
Set your own minimum and maximum delay times (in seconds) between retries.
The extension picks a random delay within your specified range, ensuring a balanced approach to retries.
Real-Time Feedback
The extension updates the browser tab’s title with a timer, so you know exactly how long it’s waiting before retrying.
It also changes the favicon to indicate the status:
Green: Everything’s good!
Yellow: Waiting for a response...
Red: Server is busy, retrying soon...
Gray: Waiting for the timeout to expire.
Smart Detection
The extension intelligently detects when DeepSeek is busy by analyzing the response content.
It only triggers the retry process when it sees the specific error messages (e.g., "The server is busy. Please try again later." or "服务器繁忙，请稍后再试").
Seamless Integration
Works seamlessly with DeepSeek’s interface. It automatically clicks the Regenerate button in the last chat block when it’s time to retry.
Console Logging
The extension provides detailed logs in the browser console to help you understand what’s happening behind the scenes. Here’s what you’ll see:
"Waiting for response...": The extension detects that DeepSeek is processing your request.
"Response received in Xs, waiting for completion...": The response is received, but the operation is still ongoing.
"Operation completed. Execution time: Xs": The operation is fully completed, and the total time is logged.
"Waiting for timeout: X seconds...": The extension is waiting for the configured delay before retrying.
"Regenerate button in the last block clicked.": The extension has successfully clicked the Regenerate button for you.
How It Works
Install the Extension
Head over to the DeepSeek Server Busy - Chrome Web Store and install the extension.
Configure Your Settings
Open the extension’s popup (click the icon in your toolbar) and set your preferred minimum and maximum delay times.
Let It Do the Work
The extension will automatically detect when DeepSeek is busy and handle the retries for you.
Why Use This Extension?
Save Time: No more manual retries. The extension does the work for you.
Reduce Frustration: Stop worrying about server errors and focus on your tasks.
Customizable: You’re in control of how long the extension waits before retrying.
Lightweight: The extension runs in the background and doesn’t slow down your browser.
Important Notes
This extension is not affiliated with DeepSeek or China. It’s a personal project I created to solve a common problem.
It’s designed to be respectful of DeepSeek’s servers. The random delays (default is set to 2-20 seconds) ensure that you’re not spamming the server with requests.
If you encounter any issues or have suggestions, feel free to reach out!
Support the Project
If you find this extension useful, consider supporting me on Get more from Simon on Patreon. Your support helps me continue improving the plugin and creating more tools like this!
Get It Now!
Ready to stop dealing with DeepSeek’s server errors? Install the extension today:
DeepSeek Server Busy - Chrome Web Store
Let me know what you think in the comments! Feedback and suggestions are always welcome.
Happy DeepSeeking!
I’m an independent developer who, like many of you, got tired of seeing DeepSeek constantly throwing the dreaded "Server is busy. Please try again later." error.
It’s frustrating, right? Having to manually click the Regenerate button over and over again is a waste of time and focus. So, I decided to do something about it!I’m excited to share DeepSeek Server Busy - Chrome Web Store, a Chrome extension that automates the retry process for you. No more manual clicking, no more frustration. Just sit back and let the extension handle it and then return back to the tab in awhile!
https://i.redd.it/cunxfu7i4xhe1.png
Key Features
Automatic Retries
When DeepSeek says the server is busy, the extension automatically retries the request for you. No more manual clicking!
It waits for a random delay (configurable by you) before retrying, so you don’t overload the server.
Customizable Delays
Set your own minimum and maximum delay times (in seconds) between retries.
The extension picks a random delay within your specified range, ensuring a balanced approach to retries.
Real-Time Feedback
The extension updates the browser tab’s title with a timer, so you know exactly how long it’s waiting before retrying.
It also changes the favicon to indicate the status:
Green: Everything’s good! Yellow: Waiting for a response... Red: Server is busy, retrying soon... Gray: Waiting for the timeout to expire.Smart Detection
The extension intelligently detects when DeepSeek is busy by analyzing the response content.
It only triggers the retry process when it sees the specific error messages (e.g., "The server is busy. Please try again later." or "服务器繁忙，请稍后再试").
Seamless Integration
Works seamlessly with DeepSeek’s interface. It automatically clicks the Regenerate button in the last chat block when it’s time to retry.
Console Logging
The extension provides detailed logs in the browser console to help you understand what’s happening behind the scenes. Here’s what you’ll see:
"Waiting for response...": The extension detects that DeepSeek is processing your request.
"Response received in Xs, waiting for completion...": The response is received, but the operation is still ongoing.
"Operation completed. Execution time: Xs": The operation is fully completed, and the total time is logged.
"Waiting for timeout: X seconds...": The extension is waiting for the configured delay before retrying.
"Regenerate button in the last block clicked.": The extension has successfully clicked the Regenerate button for you.
How It Works Install the Extension
Head over to the DeepSeek Server Busy - Chrome Web Store and install the extension.
Configure Your Settings
Open the extension’s popup (click the icon in your toolbar) and set your preferred minimum and maximum delay times.
Let It Do the Work
The extension will automatically detect when DeepSeek is busy and handle the retries for you.
Why Use This Extension? Save Time: No more manual retries. The extension does the work for you.
Reduce Frustration: Stop worrying about server errors and focus on your tasks.
Customizable: You’re in control of how long the extension waits before retrying.
Lightweight: The extension runs in the background and doesn’t slow down your browser.
Important Notes This extension is not affiliated with DeepSeek or China. It’s a personal project I created to solve a common problem.
It’s designed to be respectful of DeepSeek’s servers. The random delays (default is set to 2-20 seconds) ensure that you’re not spamming the server with requests.
If you encounter any issues or have suggestions, feel free to reach out!
Support the Project If you find this extension useful, consider supporting me on Get more from Simon on Patreon. Your support helps me continue improving the plugin and creating more tools like this!
Get It Now! Ready to stop dealing with DeepSeek’s server errors? Install the extension today:
DeepSeek Server Busy - Chrome Web StoreLet me know what you think in the comments! Feedback and suggestions are always welcome.
Happy DeepSeeking!
The plugin is not open source for now, but it's important to note that anyone can inspect the code of any Chrome extension. You can do this by unpacking the extension or using browser developer tools. In this case, the plugin operates entirely locally within your browser and does not send any external requests. This can also be verified using a network sniffer.
The only data stored are your preferences for notification settings (e.g., always on or only on errors, hidden tabs, etc.) and timeout settings. These are stored locally in your browser and are not transmitted anywhere. If I were to change the permissions or policies, Google would block the plugin, and users would need to re-enable it, agreeing to the new terms. This ensures transparency and security.
The only data stored are your preferences for notification settings (e.g., always on or only on errors, hidden tabs, etc.) and timeout settings. These are stored locally in your browser and are not transmitted anywhere. If I were to change the permissions or policies, Google would block the plugin, and users would need to re-enable it, agreeing to the new terms. This ensures transparency and security.
Similar threads
