On Thu, Dec 7, 2023 at 10:50 AM Jun Zhuang <thornbird...@yahoo.com.invalid> wrote:
> My apologies, my previous email was a mess, re-sending. > > ----------------- > > I am seeing unexpected behavior with the timer scoping. I am not using any > timer for requests in the 1st half of my test plan (DB operations only) and > only using the Gaussian timer (2 - 4 secs) in the 2nd half of the test, > i.e., in the === Create Sample Batching Job === simple controller, but it > seems to be applied universally anyway. The reason I am saying "applied > universally" is because the test runs very fast in GUI mode (~ 1 min) when > I use the run without pause option or in non-GUI mode by setting the timer > to 0. > > When I use the 2-4 seconds setting in non-GUI mode, the test ran for more > than 5 MINUTES and mostly in the 1st half the DB query part. > > The timer is placed within the last request in each of the transactions, > so my understanding is it will only happen after the last request in each > transaction. > > [image: Inline image] > > ---------- Forwarded message --------- From: Dmitri T <glin...@live.com> Date: Thu, Dec 7, 2023 at 10:39 AM Subject: Re: JMeter timer scoping issue To: JMeter Users List <user@jmeter.apache.org>, Jun Zhuang < thornbird...@yahoo.com> Timers are executed *before* each Sampler in their scope. If you want it to be executed after all Samplers you need to add a Flow Control Action < https://jmeter.apache.org/usermanual/component_reference.html#Flow_Control_Action > sampler and make the timer a child of this sampler. Or Flow Control Action sampler can create delay on its own exactly where it's placed. More information: * Scoping Rules <https://jmeter.apache.org/usermanual/test_plan.html#scoping_rules> * A Comprehensive Guide to Using JMeter Timers <https://www.blazemeter.com/blog/jmeter-timer>
