Hi, The scope of the timer is the same, I think, it applies to all sampler from it's parent level and to all its children. Make sure that the thread group has enough repetitions, then just experiment with it. Over a period of a minute, it will make sure (if possible) you make only as many requests as you want it too.
I use it by also creating a lot more threads then I really need. So there is always a thread available in order to make the requests configured in the CTT (i.e. instead of 200 threads per jmeter instance, I use 6-800). I also use other timers with no fear by using this method. Cheers, --Adrian S On Thu, Oct 18, 2012 at 9:08 AM, Tech Newbie <[email protected]> wrote: > I have a thread group that executes a set of requests > 1) login > 2) do something > 3) logout > > Now I want to introduce the constant throughput timer to execute this > entire group, at a rate of X per min. > > Where should I place my constant throughput timer? Under the thread > group? Under each request thread? I don't understand all the choices for > the "Base on" field. > > I need to make sure that all 3 steps get executed entirely and in order. > I can't have it executes the threads randomly, ie, executes step 2 without > step 1 and not follow by step 3. > > And from the GUI, what is the difference between start and "start no > pause"? > > Thanks in advance. >
