how increasing ramp
>> up time causes a problem with a sample that has a nested synchronized timer.
>>
>>
>>
>>
>> -----Original Message-----
>> From: sebb [mailto:seb...@gmail.com ]
>> Sent: Monday, August 11, 2014 8:12 PM
>> To: JMeter Users List
>
timer.
>
>
>
>
> -Original Message-
> From: sebb [mailto:seb...@gmail.com ]
> Sent: Monday, August 11, 2014 8:12 PM
> To: JMeter Users List
> Subject: Re: Where is the correct place for a synchronizing timer?
>
> I've not looked at the post in detail, but woul
d synchronized timer.
-Original Message-
From: sebb [mailto:seb...@gmail.com]
Sent: Monday, August 11, 2014 8:12 PM
To: JMeter Users List
Subject: Re: Where is the correct place for a synchronizing timer?
I've not looked at the post in detail, but would just point out that Timers are
executed
I've not looked at the post in detail, but would just point out that
Timers are executed AFTER every request that is in scope.
As such, it does not make sense to say that the timer is "at the top".
See:
http://jmeter.apache.org/usermanual/test_plan.html#scoping_rules
On 11 August 2014 23:15, Pi
I was using a synchronizing timer to best mimic a burst of http requests.
however, running a test I came across an anomaly that made me think I'm doing
it incorrectly.
I had a http request to login in users (call it "Login"), then another http
request that got something from my web site (ca
