-
Notifications
You must be signed in to change notification settings - Fork 112
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
http requests to keep using the same TCP connection #349
Comments
I have not tried this, but you could make a local modification and see if it would work. I think you would just need to change this line: https://github.com/stmcginnis/gofish/blob/main/client.go#L503 |
Thanks @stmcginnis, yes it helps
vendor1 tcp fin/ack 11 times with req.Close = true vendor1 tcp fin/ack 169 times vendor2 make no difference. Thanks. regards! |
Awesome - does this mean it works how you would like it to with that change? I'm wondering if we need to expose a config flag or something to make this easier. Or if there is value in trying to make this the default behavior. |
Hello @stmcginnis regards! |
If you're able to test with #351, that would be great to have someone else verify it improves things. |
using context and setting IdleConnTimeout and DisableKeepAlives and req.Close = false
still release the TCP for every new request.
We wanna keep the same TCP connection
Have you accomplished it?
The text was updated successfully, but these errors were encountered: