Current Guidance Around Limits?

[ShaneOH]

Hi, this is a great library, thank you for maintaining it.

I went to open this in Discussions (as was suggested here #94 (comment)) but that seems quite inactive so I wanted to ask here since I do believe it constitutes an issue, technically.

I've seen a few mentions of limit numbers:
#154 suggests 5 requests per second and up to 200k requests per day for Google
But #132 suggests being rate limited after fewer than 100 calls
#161 suggests only a few words for lingueeTranslator for example

I also read through some other issues like #149 but those weren't very useful.

So the question is: Are there any general benchmarks on how many requests this package can handle? I'm looking to translate in batches of ~50 characters but it could be bursts of many requests at once. Let's say 100 requests/second. I can pay for API access as a fallback, but building out my project, this library seemed to have incredible potential but I'm concerned about being rate limited basically right away and I can't tell if that's a consistent issue or not. Given this has 1K+ stars I'm assuming people are using it fairly heavily?

I'm basically wondering if I should spend time building my project around this library or if I should just bypass it and eat the cost of Google's API directly if I need to scale at all.

Finally, are there any more examples or explanations on how the proxies work?

Basically any guidance around limits, benchmarks, etc. would be greatly appreciated!

[vhdmoradi]

I intend to use GoogleTranslator in my api, so if the user inputs search query in other languages, I can translate them to my desired language. but, there may be a lot of users trying my api, many of them simultaniously. So, I won't be able to use this package for more than 5 requests per second?