On 13 September 2011 09:59, Shmuel Krakower <[email protected]> wrote: > Hi, > What I'm doing is calculating it like this: > > If I want a specific Sampler/iteration to be executed in a certain > frequency, for example 6000 Samples/iterations per Minute and supposed we > set 100 threads, put a timer on the thread group / sampler and calculate the > timer like this: > timer = 6000 requests / 60 seconds / 100 threads = 1 second > > in this case - I set the timer to constant 500 milliseconds and random 1000. > > > The main problem with this calculation is that it does not consider the > response time of the sample itself - so this formula is only correct if the > response time is 0. > If you want it to be more accurate, you will have to subtract the average > response time from the result. > > There is another solution for this - implemented by HP Load Runner, which is > also relevant to another discussion on the JMeter Users mailing list just > running: "Flaw in how JMeter runs threads..." > > Load Runner enables you to run the same load without being dependent on the > response time - so each iteration for each thread will start in a fixed > interval, without wait for the last iteration to finish.
In JMeter terms this would mean starting a new user thread (to make sure cookies/vars etc are maintained). It's not possible currently to start extra threads once the test has started, however one can just configure more threads initially. > (this can be configured in the Run time setting -> pacing tab of Load > Runner). > > So I think this can be useful for you and for anyone who need to run a > certain fixed load. > Without this option on JMeter we get the usual case where after certain load > the throughput gets lower instead of getting higher (response times getting > higher making the load test to generate less throughput). Only if you have not configured sufficient JMeter threads initially. > > Shmuel Krakower. > > > On Mon, Sep 12, 2011 at 9:22 AM, Raghavendra Kristam > <[email protected]>wrote: > >> Hi, >> >> I am using JMeter(2.4) for doing the loading testing of XMPP server and my >> test plan is configured as following: >> >> - Test plan >> - Thread group >> - Loop Controller >> - Java Request >> - Generate Summary Results >> - Constant timer/Constant throughput timer >> - CSV Data Set Config >> - CSV Data Set Config >> - CSV Data Set Config >> For example : >> Number of Threads: 80 >> Ramp up period: 80 >> Duration: 1800 secs >> a) If I use constant timer = 1000 milli secs then the output as follows: >> Number of samples/Throughput/Avg/Error = 129307 / 71.2/sec / 64 milli >> secs / 0.00% >> b) If I use constant throughput timer, target throughput (in samples per >> minute): 100 and Calculate throughput based on: this thread only then the >> output as follows: >> Number of samples/Throughput/Avg/Error = 214372 / 119.6/sec / 72 milli >> secs / 12.7% >> >> I need to configure the test plan to get the throughput as around 2400 >> samples per sec (144000 /min 8640000/hr). >> >> Please suggest me what timer should I use >> >> How do I calculate the number of threads / rampup period / constant timer >> values for this. >> >> >> Thanks >> >> >> >> >> >> >> --------------------------------------------------------------------- >> 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]
