[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jmeter-user
Subject:    Re: Pseudo-Interleave Controller Question
From:       Mike Darretta <michael.darretta.ctr () metnet ! navy ! mil>
Date:       2004-07-27 20:12:38
Message-ID: 4106B736.8040809 () metnet ! navy ! mil
[Download RAW message or body]

I did mean group number. This 'number' is nothing more than an arbitrary 
   sequence number for a group of requests. Related requests are bundled 
in an If-controller that checks if the randomly generated number equals 
it's assigned sequence number. So...

ThreadGroup
    |
     -- IF ${__RANDOM(1,7,REQ_NUM)}==1
          |
          -- execute Http requests for group 1
    |
    |-- IF ${REQ_NUM}==2
          |
          -- execute Http requests for group 2
    |
    |-- etc..


Jianju Liu wrote:

> Did you mean "random # = thread #"?
> 
> JJ
> 
> -----Original Message-----
> From: Mike Darretta [mailto:michael.darretta.ctr@metnet.navy.mil] 
> Sent: Tuesday, July 27, 2004 10:29 AM
> To: JMeter Users List
> Subject: Re: Pseudo-Interleave Controller Question
> 
> 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: jmeter-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]