Try structuring the plan with the timer as a child of the request like this:
+Thread Group ++Request ++++Unform Random Timer ++Request ++++Unform Random Timer You could also put one timer at the same level as the requests like this: +Thread Group ++Request ++Request ++Unform Random Timer Like this the timer will apply to each request in it's scope. By making it a child you limit its scope to the parent sampler, which gives more flexibility but adds overhead. Just using one Timer as per the second example is more concise but offers less control. ----- http://www.http503.com/ -- View this message in context: http://jmeter.512774.n5.nabble.com/How-the-Uniform-Random-Time-works-tp5166121p5166148.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
