concurrentSamples attribute
Hi,
I am using SoapUI runner to execute one of my LoadUI test case. However, I am getting absurd results in terms of TPS when I increase the value of concurrentSamples attribute of SoapUI runner from 100 to say 500 or 1000. Can some one please explain what change happens in request pattern on changing this attribute's value. Does it establish so many connections with the server?
I am using SoapUI runner to execute one of my LoadUI test case. However, I am getting absurd results in terms of TPS when I increase the value of concurrentSamples attribute of SoapUI runner from 100 to say 500 or 1000. Can some one please explain what change happens in request pattern on changing this attribute's value. Does it establish so many connections with the server?
