Thanks
Nick
Try using the RandomizeRequests option on the Options tab to randomize the requests for each thread. This will give you a better mix initially when the requests start.
To clarify - each thread runs through each session's URLs one after the other. So if you have 40 threads there will be 40 simultaneous requests going out, each thread running through each session's URLs.
The order of those requests by default is sequential, so for the first number of requests you probably see a big block of all the same urls firing because they all are processing more or less in sync. After a while they usually break out as the timings get out of sync.
If you randomize requests this should be much better, but note if you have a few very slow requests and some really quick ones you may still see some bunching.
+++ Rick ----
If I have 20 different URLs and put in a high number of threads, the threads all get taken up by calling the same URL and then moving on to the next URL. Is there anyway to call the different URLs all at once instead of calling all of them one at a time? I'm trying to load test a REST web service GET method, and calling it over and over with the same URL isnt valid.
Thanks
Nick
West Wind Technologies
Making waves on the Web
from Maui