Avoid hitting the rate limit. Don't let it fail because of it. #361
muisje
started this conversation in
Ideas & Feature requests
Replies: 2 comments 1 reply
-
|
Ah i didn't look well enough, saw some options in the settings for what i suggested, but this could be automated by looking at the response. And it still shouldn't fail because of hitting the rate limit. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Currently translation batching is a feature that covers this issue and tweaking the retry settings should be able to cover this. I am not yet feeling a specific service tweak to circumvent these settings yet. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey,
I tried this out with Google's free AI API, but i hit the rate limit and it failed to translated. I was using Gemini 3.1 Flash Lite which has a RMP of 15. Which it hit after 16 sentences. And then it failed because it got the message of the rate limit.
Mutliple things can be done to succesfully translate with this.
First thing is to continue at the suggested time 'Please retry in 165.781679ms.'.
Secondly is by trying to avoid hitting the limit by delaying requests per minute.
Third is to try to translate more than one line per request. It hit the rate limit, but the 586 / 250K TPM wasn't hit at all
And besides that if it failed it could be continued at a later moment in time continuing where it left of.
This isn't the fastest way to translate a subtitle, but it would make sure it gets translated
Beta Was this translation helpful? Give feedback.
All reactions