Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rate Limit feature for Azure/OpenAI results generation #988

Open
Jeff-ZYX opened this issue Feb 27, 2024 · 1 comment
Open

Rate Limit feature for Azure/OpenAI results generation #988

Jeff-ZYX opened this issue Feb 27, 2024 · 1 comment
Labels
💡Enhancements Something can be improved

Comments

@Jeff-ZYX
Copy link

Is your feature request related to a problem? Please describe.
Current architecture doesn't seem to support API instances with inbuilt rate limits, causing errors in generation

Describe the solution you'd like
A sleep function that can be configured to change rates of generation of GPT completions.

@chakravarthik27
Copy link
Collaborator

chakravarthik27 commented Feb 28, 2024

Hi @Jeff-ZYX

We acknowledge and appreciate the information you brought to our attention. Currently, we do not have a built-in rate restriction capability in our architecture for API instances. We understand that controlling the rate of generation is crucial to prevent errors and ensure error-free operation for GPT completions. We thank you for recommending the addition of a programmable sleep function to efficiently regulate the generating rate. We value your input and will prioritize this feature request for future updates, even though we are unable to offer a quick fix.

@chakravarthik27 chakravarthik27 added ⭐ Feature Indicates new feature requests 💡Enhancements Something can be improved v2.1.0 Issue or request to be done in v2.1.0 release and removed ⭐ Feature Indicates new feature requests labels Feb 28, 2024
@chakravarthik27 chakravarthik27 added v2.2.0 Issue or request to be done in current release and removed v2.1.0 Issue or request to be done in v2.1.0 release labels Apr 3, 2024
@chakravarthik27 chakravarthik27 added v2.3.0 released 2.3.0 and removed v2.2.0 Issue or request to be done in current release labels May 15, 2024
@chakravarthik27 chakravarthik27 removed the v2.3.0 released 2.3.0 label Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡Enhancements Something can be improved
Projects
None yet
Development

No branches or pull requests

2 participants