In my 1.5.5 suite, the majority of requests were executing with a minimum and mean time of 40-80 ms. After converting to 2.0, none of them complete in less than 110ms, not even for a static HTML resource. Is this expected in this build?
Could you share a test case, please?
I’ll take that as a “no, that is not to be expected.” I will dig in some more, and let you know what I find out.
Or just share a test case.
My bad. I forgot that the faster response times were obtained when running on a VM sitting in the same data center as the AUT. I have run two sets of tests, one on the VM and one on my laptop. In both cases, the two versions of Gatling are comparable. But the VM is much faster due to reduced network latency. So the answer is a definitive “No, there is not any slowdown induced by the new version of Gatling.” That’s good to know, though, right?
Glad to hear. I can sleep tonight.