kalli
15 years agoOccasional Contributor
Run concurrently does not seem equal to threading
Hi.
I have a HTTP load testing project with 50 virtual users, each of whom is calling the same task. Each task contains 10 connections and each connection contains 2 web requests.
To make the load test more realistic and less aggressive on the web server, I tried setting a few seconds delay in the HTTP response event handler, to make each user wait a bit before continuing on to the next request.
However, that seems to result in all the other users waiting for the currently running user.
I would have thought that if "Run concurrently" is checked, I would get a kind of a threading effect, i.e. the other users would continue with their HTTP calls regardless of the dealying user.
Is this not possible? And if so, how should I do this?
Best regards,
Karl.
I have a HTTP load testing project with 50 virtual users, each of whom is calling the same task. Each task contains 10 connections and each connection contains 2 web requests.
To make the load test more realistic and less aggressive on the web server, I tried setting a few seconds delay in the HTTP response event handler, to make each user wait a bit before continuing on to the next request.
However, that seems to result in all the other users waiting for the currently running user.
I would have thought that if "Run concurrently" is checked, I would get a kind of a threading effect, i.e. the other users would continue with their HTTP calls regardless of the dealying user.
Is this not possible? And if so, how should I do this?
Best regards,
Karl.