The issue is not related to JMeter (though it depends on what plugins you're also using, how you're using jmeter). If you made sure JMeter has enough memory, your test doesn't overwhelm the test machine, than you can rule it out.
You also have to check for any exceptions reported. The throughput is affected by response times: if the avg. would be less than 0.5s, then 2000 threads can make up to 3500-4000 hits / s. If its more then 5s, then 2000 threads can only make up to 400 hits / s. I agree with Felix about the timer policy. And you have to start monitoring your application under test to see what is going on. On Wed, Dec 7, 2011 at 11:00 AM, ZK <[email protected]> wrote: > 2000 threads is a lot > Do you run all 2000 from 1 PC? > If so you should consider distributed testing > > It sounds like you have discovered a 'bottleneck' in your system... it's up > to you to find out where that is!! > > > > > ZK > > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/How-to-increase-throughput-tp5054799p5054905.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] > >
