I think there are many ways of doing what you need but, 1 simple way is to use a ConstantThroughputTimer instead of the GaussianRandomTimer This can assist with think time and also to calculate number of users Knowing what the expected throughput vs actual throughput is also a useful metric
example: with 1 thread running, set the ConstantThroughputTimer to 60 reqs per min (60 being: number of threads * 60 = 1 req per sec per thread) So.... 1 thread = 1 req per sec if you have a think time of say 6 secs... then 1 thread with a CTP of 60 = 10 users (or a think time of 4 secs ... then 1 thread = think time / 60 = 15 users) If you did not get close to a total throughput of 60 reqs per min (1 req per sec) then you know you have problems If i wanted to simulate 300 users using this logic (with think time = 6 secs), i would have 5 threads running in 1 thread group with the ConstantThroughputTimer set to 300 (300 being: number of threads * 60 = 1 req per sec per thread) Did it make sense? HTH zilla -- View this message in context: http://jmeter.512774.n5.nabble.com/Timers-Think-Time-between-requests-and-Best-Practices-tp4410057p4413339.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
