x/net/http2: too many sockets created at high throughput #48659
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Performance
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?Note: the code is built using
$Env:GOOS = "linux"; $Env:GOARCH = "arm64"
and tested on a c4x.18xlarge aws ec2 instancego env
OutputWhat did you do?
Ran an http2 stress-test, client and server on different machines but same VPC. testing with traffic gradually increasing - going up-to 20K requests/second (although issue occured before that limit)
In a separate shell, ran
lsof -p <pid> | wc -l
to monitor the used socketsThis was done in 2 situations
client.go
client.go
Outputserver.go
server.go
OutputWhat did you expect to see?
lsof -p <pid> | wc -l
would gradually increase.What did you see instead?
lsof -p <pid> | wc -l
jumped .Go routine dump of client
the overwhelming majority of goroutines are stuck at
h2_bundle.go:763
go routine sample dump
OutputThe text was updated successfully, but these errors were encountered: