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.

Sign up for GitHub

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

Jump to bottom

Considering "retry-after" header as well when retrying throttled requests. #31

Open
sushaanttb opened this issue Feb 21, 2024 · 0 comments · May be fixed by #48
Open

Considering "retry-after" header as well when retrying throttled requests. #31

sushaanttb opened this issue Feb 21, 2024 · 0 comments · May be fixed by #48

Comments

@sushaanttb
Copy link
Contributor

Currently, we are only considering "retry-after-ms" when throttling requests.

image image

But as with 429 errors, we can also receive "retry-after" header (which would provide the time value in seconds) ,should we not consider that header too in our logic?

Azure documentation ref. :
image
https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/provisioned-throughput
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added handling considering retry-after header sushaanttb/azure-openai-benchmark
1 participant
@sushaanttb