Gotling opening up new TCP connection for each request

[prashantgupta24]

I am monitoring open connections made by gotling on nginx, and I saw that gotling opened a new connection for each request.

So for instance if I had 100 users, each with 10 iterations, gotling made a total of 1000 new TCP connections to nginx.

I'm not sure if this was the intended behavior, but I did some research, and by moving the code below in httpreq.go to outside the function DoHttpRequest (basically making it a global variable):

var DefaultTransport http.RoundTripper = &http.Transport{
	TLSClientConfig: &tls.Config{InsecureSkipVerify: true},
}

reduced the number of new TCP connections.

My guess is that gotling started utilizing persistent connections after this change?

Love to hear your thoughts on this.

[eriklupander]

Hi, sorry I havn't gotten back to you regarding your question.

If I remember correctly: When I originally developed Gotling I used it to load-test an environment set up behind a Zuul Edge Server in a Docker Swarm based landscape. I vaguely recall that I had to deliberately disable HTTP keep-alives i Gotling in order for Docker Swarm to properly load-balance requests amongst targeted containers.

I guess this is something that one should consider making configurable on a "per-action" or possibly "per suite" in the yaml.