You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Scott Pack <sc...@vykor.com> on 2005/05/03 20:49:37 UTC
Scoping rules and behavior of Constant Timer
What is the expected behavior of the Constant Timer as a child of a Sampler (HTTP for example)? The documentation states that this component is 'strictly hierarchical', however what I find is not consistent with this statement. Here is the script:
Test Plan
--->Thread Group 1
---->---->Loop Controller (5 iterations)
---->---->---->HTTP Request 1.1
---->---->---->---->Constant Timer (10000)
---->---->---->HTTP Request 1.2
---->---->---->HTTP Request 1.3
Actual: Every ten seconds, requests 1.1 - 1.3 are issued sequentially without delay between requests, i.e. 1.1 -> 1.2 -> 1.3 -> sleep 10sec -> 1.1 -> 1.2 -> 1.3 -> sleep 10sec...
Expected: 10 second delay after request 1.1, no delay between other requests, i.e. 1.1 -> sleep 10sec -> 1.2 -> 1.3 -> 1.1 -> sleep 10 sec...
Thus it appears there is no way to set a timer for an individual sampler that needs extra time (such as submitting form data...) within a loop controller.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Scoping rules and behavior of Constant Timer
Posted by Michael Stover <ms...@apache.org>.
It's doing what it's supposed to, but delays come before their target
samplers...
-Mike
On Tue, 2005-05-03 at 11:49 -0700, Scott Pack wrote:
> What is the expected behavior of the Constant Timer as a child of a Sampler (HTTP for example)? The documentation states that this component is 'strictly hierarchical', however what I find is not consistent with this statement. Here is the script:
>
> Test Plan
> --->Thread Group 1
> ---->---->Loop Controller (5 iterations)
> ---->---->---->HTTP Request 1.1
> ---->---->---->---->Constant Timer (10000)
> ---->---->---->HTTP Request 1.2
> ---->---->---->HTTP Request 1.3
>
> Actual: Every ten seconds, requests 1.1 - 1.3 are issued sequentially without delay between requests, i.e. 1.1 -> 1.2 -> 1.3 -> sleep 10sec -> 1.1 -> 1.2 -> 1.3 -> sleep 10sec...
> Expected: 10 second delay after request 1.1, no delay between other requests, i.e. 1.1 -> sleep 10sec -> 1.2 -> 1.3 -> 1.1 -> sleep 10 sec...
>
> Thus it appears there is no way to set a timer for an individual sampler that needs extra time (such as submitting form data...) within a loop controller.
>
>
>
> ---------------------------------------------------------------------
> 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: Scoping rules and behavior of Constant Timer
Posted by Peter Lin <wo...@gmail.com>.
the constant timer attempts to send requests to meet the constant
rate. which means it sends requests and sleeps for x time until it
should do it again.
so I'm guessing what you want is constant and spread out evenly.
peter lin
On 5/3/05, Scott Pack <sc...@vykor.com> wrote:
> What is the expected behavior of the Constant Timer as a child of a Sampler (HTTP for example)? The documentation states that this component is 'strictly hierarchical', however what I find is not consistent with this statement. Here is the script:
>
> Test Plan
> --->Thread Group 1
> ---->---->Loop Controller (5 iterations)
> ---->---->---->HTTP Request 1.1
> ---->---->---->---->Constant Timer (10000)
> ---->---->---->HTTP Request 1.2
> ---->---->---->HTTP Request 1.3
>
> Actual: Every ten seconds, requests 1.1 - 1.3 are issued sequentially without delay between requests, i.e. 1.1 -> 1.2 -> 1.3 -> sleep 10sec -> 1.1 -> 1.2 -> 1.3 -> sleep 10sec...
> Expected: 10 second delay after request 1.1, no delay between other requests, i.e. 1.1 -> sleep 10sec -> 1.2 -> 1.3 -> 1.1 -> sleep 10 sec...
>
> Thus it appears there is no way to set a timer for an individual sampler that needs extra time (such as submitting form data...) within a loop controller.
>
> ---------------------------------------------------------------------
> 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