API calls to davinci text 3 very slow and random speeds for identical prompts

API Feedback
2

besides the speed issue when requests are completed with status 200

we also get a lot of these:
Error: {
“error”: {
“message”: “The server had an error while processing your request. Sorry about that!”,
“type”: “server_error”,
“param”: null,
“code”: null
}
}

3

This is discussed in this thread:

So far, the OpenAI team has not responded… we are all experiencing the same thing, and waiting on a fix. The “The server had an error while processing your request. Sorry about that!” server_error makes it impossible to use davinci-003 at the moment.

4

are you having speed issues also when requests are successful?

1 Like
5

Yes, things are going slow as well, but the main issue is the server_error, which is completely breaking every few requests. I’m assuming both are caused by the same issue.

6

Same problem, 30-55 sec for a request or got an error

7

Any answers about this? Getting up to a minute per request via the API. This is for around 500 to 1000 tokens total.

8

They say it’s resolved, but it’s clearly getting worse and worse.

1 Like
9

I ahve the same issue since this morning, it started a little on Thrusday then I added a delay of 4sec between each call but since this morning I always get the error : 500 {‘error’: {‘message’: ‘Internal server error’, ‘type’: ‘auth_subrequest_error’, ‘param’: None, ‘code’: ‘internal_error’}}

what can I do to fix this ?

2 Likes
10

Openai have just posted that it has been investigated and resolved in playground and the api

11

API Requests, to Davinci Text 3, from the UK: On 5th February 2023, the API was returning responses within seconds. Today, responses are closer to 1 minute. This is a disaster for a planned demo that will now need to be rescheduled. So, the issue is not resolved for me.

12

Same. It is not good for showing of prototypes. Everyone will be looking at their watches…

13

Just got some Testers for my MVP and the API slowed down to a point where it times out constantly. What an unlucky timing. Until yesterday it was working just fine through extensive testing.

14

It’s horrible. Getting random 429 errors and it takes a very long time to generate even the simplest answers (1 minute seems like the new normal). I’m on a paid account. I have these issues for over a week now; before it was much faster and I rarely got these weird 429 errors.

15

I use AWS east coast servers. When I was testing from the cmd line 3-4 weeks back, I used to see frequent 429s. But now I rarely do. My app users are in Asia & USA. So, we cover the entire 24h span.

Also, wrt latencies, I routinely see 3-10secs. Which I thought was terrible:)

16

I can confirm this is the same here in Germany. It got a bit better today, and the response time often get back to normal in the evening time (central European time); but the response time is much worse than what it used to be. (davinci-3, completion api)

17

The slow API is still an issue when trying from California.

18

Can you show your code, please? We might be able to help.

19

it’s not a matter of code,
the speed has improved drastically now, but the quality is down, we are seing a lot more “junk” or hallucinations returned now for the same prompts, I guess they are balancing between quality of output and performance

20

For me the latency has gotten worse. It takes about 13 seconds to get a response from davinci. What is the issue?

21

Any progress about that ? Same problems here (France)