Well, I've found my own answer. I use the __Random function prior to
each request group, and only issue the request if the randomly generated
sequence number == the group number.
Mike
Mike Darretta wrote:
My test contains a number of HTTP requests to modify page
configurations. I would like a pattern that would allow each thread to
either randomly or in some orderly way select a different configuration
request, independent of other threads.
I thought the Interleave Controller would solve this issue, but it
appears to only control requests per iteration, not per thread.
So, instead of :
Loop1
Thread 1 -> execute request 1
Thread 2 -> execute request 1
Thread 3 -> execute request 1
Loop2
Thread 1 -> execute request 2
Thread 2 -> execute request 2
Thread 3 -> execute request 2
etc...
I would like:
Loop1
Thread 1 -> execute request 1
Thread 2 -> execute request 2
Thread 3 -> execute request 3
Loop1
Thread 1 -> execute request 2
Thread 2 -> execute request 3
Thread 3 -> execute request 1
etc...
The only way I can see doing this is to create separate ThreadGroups for
each thread in question. This is not practical, since I plan on running
for over 100 threads.
Any thoughts?
Thanks,
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
