-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Regression: Client keep-alive subsequent requests very slow #1997
Comments
Additional: |
Correction - reducing the read timeout to 3s results in subsequent requests taking 3s. Setting the timeout longer than 4-5s does not change the 4-5s behavior. |
Tracked down the exact version the problem was introduced... |
@nickkelsey could you try this version? Ref: #1969 |
I see "std::this_thread::sleep_for(microseconds{interval_usec});" added, but no change to the problem unfortunately. |
If I revert the code in the two places where the new is_ssl_peer_could_be_closed() function is invoked everything works. |
Could you point the commit that starts causing the problem? Thanks! |
Commenting out the call to is_ssl_peer_could_be_closed() in ClientImpl::send_ avoids the problem. |
Thanks for your help! I'll look into it when I have time. |
Linux, Client mode, OpenSSL and Poll defines set, keep-alive enabled, comparing 0.13.3 with 0.18.2.
Server is running Apache2 delivering static files, Content-Length used.
The first GET request takes about 200ms as expected.
With 0.13.3 the second and subsequent requests take around 60ms as expected.
With 0.18.2 the second and subsequent requests take anywhere from 4000ms to 5000ms.
If I don't enable keep-alive the requests takes around 200ms as expected.
The text was updated successfully, but these errors were encountered: