-
-
Notifications
You must be signed in to change notification settings - Fork 516
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
Timeout with GPT-4, stream = true required #80
Comments
Hi @Pierquinto I am able to use GPT-4 without any problems. Can you give us a concrete example when you run into the timeout issue? After our last release in the past days we are now able to continue making the client capable of streamed responses. I will give you an update as soon as possible. |
I am also keep getting a lot of "Idle timeout reached" for model gpt-3.5-turbo chat requests:
|
change your php.ini and apache settings. |
How did y'all get access to the GPT 4 api already 😢 |
Are you able to offer examples of this? I too have been having issues streaming GPT-4. I can do it with 3.5 but 4 keeps timing out (I keep hitting the 30s timeout on AWS (Vapor)). I know some of the timeouts with 3.5 over the weekend were network related as they have been having many issues, but I would love to know how to properly set this up in production. Locally, it streams fine--but obviously this is less than ideal for paying users. |
I don't know about AWS. But i needed to set additional nginx directives on my server: proxy_connect_timeout 360s; Maybe that helps ... Cheers! |
Hi @Pierquinto Hope our release yesterday resolved your issues with GPT-4. Otherwise don't hesitate to reopen the issue. |
we are seeing lots of timeouts even though our timeout is set to 8 mins! This is with GPT-4. GPT3.5 works fine but has such a small token limit that it doesn't work for our use case |
I'm still seeing this pop up in the latest version (0.7.3), specifically for the GPT-4 model. It occurs exactly at 30 seconds, so it's clearly some kind of timeout. But strange that this doesn't also happen for GPT-3.5, only for GPT-4 model. But I've already set every Nginx and PHP setting that I know of: Nginx: proxy_read_timeout 360s;
proxy_connect_timeout 20s;
proxy_send_timeout 360s;
client_body_timeout 360s;
fastcgi_buffers 16 32k;
fastcgi_buffer_size 64k;
fastcgi_busy_buffers_size 64k;
fastcgi_connect_timeout 360s;
fastcgi_send_timeout 360s;
fastcgi_read_timeout 360s; PHP: request_terminate_timeout = 180 |
the same for me |
It seems that with GPT-4 it takes too long to receive a response from APIs. In the reference they mention this stream = true to start receiving the first tokens immediately and avoiding a timeout.
The text was updated successfully, but these errors were encountered: