Well, iteration count is only used for debugging or when creating new samplers only. I would gladly share my test plan with you if you want to look at it. I already posted the requirements for the test. This system has over a dozen consumers and exposes over 120 services. So each service must be hit independently which is why a separate thread group is needed for each sampler. This is my first jmeter test plan and I don't doubt that I may be doing something fundamentally wrong.
> Date: Sat, 10 Mar 2012 22:57:54 -0800 > From: [email protected] > To: [email protected] > Subject: Re: Constant Throughput Timer and test duration conflict > > If you operate with fixed test duration, then iteration count makes no sense, > because the same test duration may include different iterations, depending > on server response time. > Well, all I hear about your case tells me that there's something may be > inefficient in your approach. > Maybe you should choose stress-test mode as your primary performance > criteria. Just my opinion. > > ----- > -- > Andrey Pohilko > JP@GC Maintainer > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/Constant-Throughput-Timer-and-test-duration-conflict-tp5533559p5554206.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] >
