jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Speteanu <asp.ad...@gmail.com>
Subject Re: Constant Timer behaviour
Date Mon, 10 Sep 2012 11:43:24 GMT
Hi,

Timers and Listeners apply to their parent and from their parent level down
to all children of its parent (the structure is tree like).

Therefore, when you add a timer in a controller or thread group, it will
apply to all samplers  in the controller/thread group. The way you added
the 300ms timer in the middle of the two thread groups is irrelevant.
Again, it will apply to the parent, and thus the position is irrelevant.
The parent is the test plan and therefore the 300ms timer will apply to all
samplers in both thread groups. A sampler will wait for the sum of all
timers that it is in the scope of. In your example each sampler should wait
5000ms + 300ms. There are other more complex scenario (like when you use
random timers, throughput timers.)

Read on it and experiment a little with dummy test plans (that have few
samplers).

--Adrian S

On Fri, Sep 7, 2012 at 3:13 AM, Divya <divyasingh26@gmail.com> wrote:

> Hi Guys,
>
> Can someone please confirm the Constant Timer behavior. For instance,
> Adding a Constant Timer under a Thread group will add a wait time/think
> time between all the Http Request Sampler execution for each single Thread
> ?
>
>
> Scenario:
>
> Test Plan
>  ------ Thread group 1
>                 ------ *Constant Timer* (5000 ms)
>                 ------ Http Request Sampler 1
>                 ------ Http Request Sampler n
>
> ------- *Constant Timer* (300 ms)
>
> ------- Thread group 2
>                 ------ *Constant Timer* (5000 ms)
>                 ------ Http Request Sampler 1
>                 ------ Http Request Sampler n
>
>
> Thanks,
> D
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message