Hi, Not being able to achieve target throughput is not always related to things that are wrong on the test client (considering that 25 rps seems rather low ), but rather with applications deployed in a state that is not ready to handle the generated traffic. The advise below is very good, so that you eliminate common/obvious mistakes client-side. But I also suggest you keep an eye for possible application & setup specific problems.
Cheers, Adrian S On Thu, May 23, 2013 at 12:30 AM, Shmuel Krakower <[email protected]>wrote: > Things you may try: > 1. Remove the Throughput controller and see what happens. > 2. Add more threads and see what happens. > 3. Is your load machine is overkilled (CPU at 100%, etc...)? > 4. If all above leaves you with same limit of about 25MPS it might be the > target service which cannot handle anymore load. Try: > a. Running at the same time, the same load from another machine and see if > you get to 50MPS in total or still you get about 25... > b. Look into the service under load and try to figure out what is the > bottleneck > c. Maybe something else between the two machines which runs JMeter and the > Service is limiting you? (i.e. internet connection limits) > > > > Shmuel Krakower. > www.Beatsoo.org - re-use your jmeter scripts for application performance > monitoring from worldwide locations for free. > > > On Wed, May 22, 2013 at 6:48 PM, Sameera Rao P <[email protected] > >wrote: > > > Hi > > > > I Am using soap sample xml / RPC and trying to post ebxml messages. I am > > not able to achieve my load of 100 Messages Per second running from GUI. > > I tried using constant throughput timer with 15 threads ,but still not > > able to go beyond 25MPS. Can you please suggest the solution for > > achieving the load > > > > Thanks & Regards > > Sam > > > > > > > ============================================================================================================================Disclaimer: > > This message and the information contained herein is proprietary and > > confidential and subject to the Tech Mahindra policy statement, you may > > review the policy at <a href=" > http://www.techmahindra.com/Disclaimer.html > > ">http://www.techmahindra.com/Disclaimer.html</a> externally and <a > href=" > > http://tim.techmahindra.com/tim/disclaimer.html";> > > http://tim.techmahindra.com/tim/disclaimer.html</a> internally within > > Tech > > > Mahindra.============================================================================================================================ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
