You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by sebb <se...@gmail.com> on 2007/08/23 22:58:42 UTC
Re: Timers
Timers are applied to all samplers in scope, and are applied before
the sampler executes.
On 23/08/07, Aditi Seth (adseth) <ad...@cisco.com> wrote:
> Hi ,
>
> I am trying to setup a test plan where each request has a delay
> associated with it and each of these delays are different.
>
> Example
>
> Thread group
> -simple controller
> gaussian random timer
Cannot tell where this is in the test plan.
If it is the only child of the simple controller, then it will not
apply to any samplers.
If it is at the same level as the samplers below, then it will apply
to all of them.
> - login
> - http request A ( delay 1 min)
Where is the timer?
> - http request B
> - gaussian random timer ( delay 5 mins)
Will apply to B only
> - http request C
> - gaussian random timer (delay 10 mins)
Will apply to C only
>
>
> Bascially, each user access page A every min, page B once in 5 mins and
> page C once in 10 mins. And the login request needs to be shared between
> these requests.
>
> I did try to add timers to each request , but the flow is sequential.
> Request A is now delayed by sum of all these timers.
> Do I need different thread groups for this scenario? Or is there any
> other nice trick that I am missing.
>
> Thanks,
> Aditi
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Timers
Posted by sebb <se...@gmail.com>.
On 23/08/07, Aditi Seth (adseth) <ad...@cisco.com> wrote:
> Thanks for the quick reply.
>
> From what I understand all requests are processed in a sequential
> manner.
Yes.
> I am currently executing these requests in a loop - thus after
> the last request with a delay of 10 mins is done, only then does the
> first request go out again.
No - as I wrote in my last message, timers are applied BEFORE the
samplers to which they apply.
> Effectively the first request has a
> cumulative delay of 10+ mins each run? Is that correct?
No.
> I would like the first request to go out every 1 min and the last every
> 10 mins. Is this possible with jmeter?
Do you mean that in a 10 minute period, the first request will be
repeated 10 times, and the last just once?
If so, then the example below will not work.
> Example -
>
> Thread group ( loop forever)
> Simple Controller
> - HTTP request
> - gaussian timer (1 min)
> Simple Controller
> -Logon user
> - gaussian timer (1 min)
> -http request
> -gaussian timer (1 min)
> - http request
> - gaussian timer ( 10 mins)
>
>
You could try:
Loop Controller (10 times)
- HTTP 1
- - Timer 1 min
HTTP 2
Or you could use the
http://jakarta.apache.org/jmeter/usermanual/component_reference.html#Throughput_Controller
as parent of the last HTTP request.
> Thanks for your help,
>
> Aditi
>
>
> -----Original Message-----
> From: sebb [mailto:sebbaz@gmail.com]
> Sent: Thursday, August 23, 2007 1:59 PM
> To: JMeter Users List
> Subject: Re: Timers
>
> Timers are applied to all samplers in scope, and are applied before the
> sampler executes.
>
>
> On 23/08/07, Aditi Seth (adseth) <ad...@cisco.com> wrote:
> > Hi ,
> >
> > I am trying to setup a test plan where each request has a delay
> > associated with it and each of these delays are different.
> >
> > Example
> >
> > Thread group
> > -simple controller
> > gaussian random timer
>
> Cannot tell where this is in the test plan.
> If it is the only child of the simple controller, then it will not apply
> to any samplers.
> If it is at the same level as the samplers below, then it will apply to
> all of them.
>
> > - login
> > - http request A ( delay 1 min)
>
> Where is the timer?
>
> > - http request B
> > - gaussian random timer ( delay 5 mins)
>
> Will apply to B only
>
> > - http request C
> > - gaussian random timer (delay 10 mins)
>
> Will apply to C only
>
> >
> >
> > Bascially, each user access page A every min, page B once in 5 mins
> > and page C once in 10 mins. And the login request needs to be shared
> > between these requests.
> >
> > I did try to add timers to each request , but the flow is sequential.
> > Request A is now delayed by sum of all these timers.
> > Do I need different thread groups for this scenario? Or is there any
> > other nice trick that I am missing.
> >
> > Thanks,
> > Aditi
> >
>
> ---------------------------------------------------------------------
> 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
RE: Timers
Posted by "Aditi Seth (adseth)" <ad...@cisco.com>.
Thanks for the quick reply.
>From what I understand all requests are processed in a sequential
manner. I am currently executing these requests in a loop - thus after
the last request with a delay of 10 mins is done, only then does the
first request go out again. Effectively the first request has a
cumulative delay of 10+ mins each run? Is that correct?
I would like the first request to go out every 1 min and the last every
10 mins. Is this possible with jmeter?
Example -
Thread group ( loop forever)
Simple Controller
- HTTP request
- gaussian timer (1 min)
Simple Controller
-Logon user
- gaussian timer (1 min)
-http request
-gaussian timer (1 min)
- http request
- gaussian timer ( 10 mins)
Thanks for your help,
Aditi
-----Original Message-----
From: sebb [mailto:sebbaz@gmail.com]
Sent: Thursday, August 23, 2007 1:59 PM
To: JMeter Users List
Subject: Re: Timers
Timers are applied to all samplers in scope, and are applied before the
sampler executes.
On 23/08/07, Aditi Seth (adseth) <ad...@cisco.com> wrote:
> Hi ,
>
> I am trying to setup a test plan where each request has a delay
> associated with it and each of these delays are different.
>
> Example
>
> Thread group
> -simple controller
> gaussian random timer
Cannot tell where this is in the test plan.
If it is the only child of the simple controller, then it will not apply
to any samplers.
If it is at the same level as the samplers below, then it will apply to
all of them.
> - login
> - http request A ( delay 1 min)
Where is the timer?
> - http request B
> - gaussian random timer ( delay 5 mins)
Will apply to B only
> - http request C
> - gaussian random timer (delay 10 mins)
Will apply to C only
>
>
> Bascially, each user access page A every min, page B once in 5 mins
> and page C once in 10 mins. And the login request needs to be shared
> between these requests.
>
> I did try to add timers to each request , but the flow is sequential.
> Request A is now delayed by sum of all these timers.
> Do I need different thread groups for this scenario? Or is there any
> other nice trick that I am missing.
>
> Thanks,
> Aditi
>
---------------------------------------------------------------------
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