-
Notifications
You must be signed in to change notification settings - Fork 17.5k
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
crypto/tls: Conn.rawInput buffer has no chance to shrink on large number of idle conns #43563
Comments
/cc @FiloSottile |
I assume this is after the #42035 fix? |
Yes |
I'm very interested in this topic as well. Any progress on this issue and the linked PR? |
I don't have a good enough server to test this PR, maybe the bench data is not convincing |
@FiloSottile Is there any news? Because I have the same issue with golang 1.17.3 . |
* coap-gateway: update go-coap * docker: patch tls.Conn for shrink connection buffer golang/go#43563 * fix for CR
Change https://golang.org/cl/370581 mentions this issue: |
@FiloSottile Any update? |
This comment was marked as duplicate.
This comment was marked as duplicate.
It seems |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What did you do?
Open TLS on HTTP server.
TLS HTTP server:
TLS HTTP client.
./client 40000 1000 https://ip:1234/
This TLS HTTP server costs about 2.2GB RSS.
To reduce the memory cost, we shrink the TLS read buffer when read timeout:
And the memory usage decreased from 2.2GB to around 560 MB
But I don't know whether this is a proper fix.
If it is. I'm happy to open a PR for this
The text was updated successfully, but these errors were encountered: