I just have one constant throughput timer at the end of the test, i.e after 24 samples.
==================== sebb-2-2 wrote: > > I think your problem might be due to the placement of the Timer. > > Timers are activated for every sampler which is in scope. > > Probably best to add the Timer as a child of just one of the samples. > > On 15/11/2007, tiffany <[EMAIL PROTECTED]> wrote: >> >> From the user manuel, it said the calculations is to keep the total >> throughput (in terms of samples per minute) . >> >> I have a test case which has 24 samples and the following configuration: >> >> Threads : 10 >> Ramp up period: 60 >> Iterations: 100 >> >> I need frequency =20/hr. >> >> My calculation : The entire test case (24 samples) needs to finish every >> 3 >> minutes in order to have 20 times per hour. So each sample needs 7.5 sec >> to >> execute. Based on this, I should set "Target throughput (in samples per >> minute)" = 3.0. >> >> But >> >> "Based on my testing with 1 thread, I need to set the "Target throughput >> (in >> samples per minute)" = 8.0 in order to obtain 3 minutes to finish that >> test? >> >> In my configuration, I need to have 10 threads,what should I set for the >> "Target throughput (in samples per minute)" >> >> if I set "Calculate Throughput based on" = this thread only? >> >> if I set "Calculate Throughput based on" = all active threads in current >> thread group ? >> >> >> Thanks, >> Tiffany >> >> >> >> >> >> >> >> =========== >> >> sebb-2-2 wrote: >> > >> > On 14/11/2007, tiffany <[EMAIL PROTECTED]> wrote: >> >> >> >> I am using "all active threads in current thread group", what does >> this >> >> mean >> >> if I have the following configuration? Do I have to care number of >> >> threads >> >> in this case to configure the constant throughput timer? >> >> >> >> threads: 10 >> >> Ramp up period: 60 >> > >> > Every 6 seconds, another thread becomes active. >> > >> >> constant throughput timer: 17.0 ( I want to have frequency=100/hr). >> > >> > 17.0 * 60 = 1020./hour >> > >> > You need 100/60 = 1.66/minute. >> > >> > It's basic arithmetic ... >> > >> >> Iterations: 100 >> >> >> >> ============ >> >> >> >> sebb-2-2 wrote: >> >> > >> >> > On 09/11/2007, tiffany <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> The calculations is based on 1 thread (1 user) or number of threads >> >> >> doesn't >> >> >> count? >> >> >> >> >> >> Actually, I have a test with the following configuration: >> >> >> >> >> >> threads: 1 >> >> >> iterations: 100 >> >> >> constant throughput timer: 30.0 (all active threads in current >> thread >> >> >> group) >> >> >> >> >> >> Frequency needs per hour: 200 >> >> >> >> >> >> By the calcuation: I should put 3.33 per min. I tried it to run >> with >> >> >> constant throughput timer: 3.33 (all active threads in current >> thread >> >> >> group) >> >> >> , it did't give me the right frequency( in hr), >> >> > >> >> > what did it give? >> >> > >> >> >> by testing, I figure it out, >> >> >> I need to set constant throughput timer: 30.0 in order to have >> >> frequency= >> >> >> 200 /hr. >> >> >> >> >> >> I don't really understand this. What about if threads=120, what >> should >> >> I >> >> >> set >> >> >> in constant throughput timer?? >> >> > >> >> > If you are using anything but "this thread only", then it does not >> >> > matter how many threads there are - the delays are calculated as >> >> > needed to provide the throughput. >> >> > >> >> >> >> >> >> ================= >> >> >> >> >> >> sebb-2 wrote: >> >> >> > >> >> >> > 200 per hour=200/60 per min=3.33 per min >> >> >> > >> >> >> > On 18/09/2007, tiffany <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> >> >> Thanks for the answer. >> >> >> >> >> >> >> >> I still have a question, if I want my test case which consists 9 >> >> >> requests >> >> >> >> run 200 times per hour. How to calculate the throughput time for >> >> >> it(What >> >> >> >> should I set in the Constant Throughput Timer ?) >> >> >> >> >> >> >> >> Thanks, >> >> >> >> Tiffany >> >> >> >> ===================== >> >> >> >> >> >> >> >> sebb-2 wrote: >> >> >> >> > >> >> >> >> > Constant Timer always sleeps for the amount of time specified. >> >> >> >> > >> >> >> >> > Constant Throughput Timer sleeps for as long as necessary to >> try >> >> and >> >> >> >> > maintain the throughput. >> >> >> >> > >> >> >> >> > On 13/09/2007, tiffany <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> >> >> >> >> Hi, >> >> >> >> >> >> >> >> >> >> I am not sure the difference % the usage of Constant Timer >> and >> >> >> >> Constant >> >> >> >> >> throughput timer even I have read the user manual. >> >> >> >> >> >> >> >> >> >> I try to do a web load test with 3 test cases, all 3 test >> cases >> >> are >> >> >> in >> >> >> >> a >> >> >> >> >> test plan as the following: >> >> >> >> >> >> >> >> >> >> - test plan >> >> >> >> >> - thread group 1 >> >> >> >> >> - HTTP request >> >> >> >> >> - other requests... >> >> >> >> >> - constant timer/constant throughput timer >> >> >> >> >> - thread group 2 >> >> >> >> >> - HTTP request >> >> >> >> >> - other requests... >> >> >> >> >> - constant timer/constant throughput timer >> >> >> >> >> - thread group 3 >> >> >> >> >> - HTTP request >> >> >> >> >> - other requests... >> >> >> >> >> - constant timer/constant throughput timer >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> What is the difference of using constant timer and constant >> >> >> throughput >> >> >> >> >> timer >> >> >> >> >> in each thread group? Actually, I try to create a test plan >> with >> >> 3 >> >> >> >> test >> >> >> >> >> cases on it and each test case needs to run with different >> >> >> frequency. >> >> >> >> For >> >> >> >> >> example : >> >> >> >> >> test case 1 needs to run 20 times per >> hour, >> >> >> >> >> test case 2 needs to run 100 times per >> hour, >> >> >> >> >> test case 3 needs to run 60 times per >> hour. >> >> >> >> >> >> >> >> >> >> What timer should I use in the above case? >> >> >> >> > >> >> >> >> > Constant Throughput Timer. >> >> >> >> > >> >> >> >> >> Thanks, >> >> >> >> >> Tiffany >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> View this message in context: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> http://www.nabble.com/Constant-Timer-vs-Constant-throughput-timer-tf4437423.html#a12660224 >> >> >> >> >> Sent from the JMeter - User mailing list archive at >> Nabble.com. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> >> >> To unsubscribe, e-mail: >> >> [EMAIL PROTECTED] >> >> >> >> >> For additional commands, e-mail: >> >> >> [EMAIL PROTECTED] >> >> >> >> >> >> >> >> >> >> >> >> >> >> > >> >> >> >> > >> >> >> >> --------------------------------------------------------------------- >> >> >> >> > To unsubscribe, e-mail: >> >> [EMAIL PROTECTED] >> >> >> >> > For additional commands, e-mail: >> >> [EMAIL PROTECTED] >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> >> >> >> >> -- >> >> >> >> View this message in context: >> >> >> >> >> >> >> >> >> >> http://www.nabble.com/Constant-Timer-vs-Constant-throughput-timer-tf4437423.html#a12762992 >> >> >> >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> >> To unsubscribe, e-mail: >> [EMAIL PROTECTED] >> >> >> >> For additional commands, e-mail: >> >> [EMAIL PROTECTED] >> >> >> >> >> >> >> >> >> >> >> > >> >> >> > >> >> --------------------------------------------------------------------- >> >> >> > To unsubscribe, e-mail: >> [EMAIL PROTECTED] >> >> >> > For additional commands, e-mail: >> [EMAIL PROTECTED] >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >> -- >> >> >> View this message in context: >> >> >> >> >> >> http://www.nabble.com/Constant-Timer-vs-Constant-throughput-timer-tf4437423.html#a13673859 >> >> >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> >> For additional commands, e-mail: >> [EMAIL PROTECTED] >> >> >> >> >> >> >> >> > >> >> > >> --------------------------------------------------------------------- >> >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> > For additional commands, e-mail: [EMAIL PROTECTED] >> >> > >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Constant-Timer-vs-Constant-throughput-timer-tf4437423.html#a13753103 >> >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Constant-Timer-vs-Constant-throughput-timer-tf4437423.html#a13763014 >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Constant-Timer-vs-Constant-throughput-timer-tf4437423.html#a13767447 Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
