You may also give a try to the JMeterPlugins Ultimate Thread Group. Google for it, it makes the load test structure visible so you can see how many users/threads you will have in any given time.
Shmuel Krakower. www.Beatsoo.org - re-use your jmeter scripts for application performance monitoring from worldwide locations for free. On Wed, Oct 2, 2013 at 1:19 PM, bobMeliev <[email protected]> wrote: > Rampup period must be similar to number of users for the reason not to > crash > system at the beginning. Set Iteration=Forever, Number of threads=2000, > Rampup period=2000(hope your system handles such load :)). In first > iteration each sampler will start with 1 second delay, this means after > 2000 > seconds you can get load with about 2000 active users. If you can generate > such report I recommend to use Jmeter plugin > < > http://community.blazemeter.com/knowledgebase/articles/83191-blazemeter-plugin-to-jmeter > > > for reporing. If you use plugin in reporting mode you can exclude all > linteners and they won't charge you, as a result you get cool chart report. > > > > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/Ramp-up-period-doesn-t-correspond-to-duration-of-test-tp5718272p5718284.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] > >
