wallarm/gotestwaf

No way to tune MaxIdleConnsPerHost

dankegel opened this issue · 0 comments

https://go.dev/src/net/http/transport.go says

// DefaultMaxIdleConnsPerHost is the default value of Transport's
// MaxIdleConnsPerHost.
const DefaultMaxIdleConnsPerHost = 2

Tuning just MaxIdleConns isn't enough; you also need to be able to tune MaxIdleConnsPerHost.
Otherwise your effective connection pool isn't the size you thought it was!

Fortunately, setting them to the same value is close enough to right, so it's probably overkill to change the UI.