Ted87
Ted87

Reputation: 81

Performance test using Jmeter - Tune the Script as per requirement

I have to do performance test on our API. In our current system they told 3500 request are handling per minute. But there is no way to take the amount of concurrent users per minute. So I just run my script for one user and it takes 1 minute to run all 39 request. Then I execute for 1000 users. In That case I set my Tread Group as follows

enter image description here

Then by system get completely crashed on 21min enter image description here

Summary report is as follows: enter image description here

I'm confusing what will be the exact test that I needs to run to test my requirement.(Req:- System handle 3500 request per minute)

Kindly help me to sort out this properly

Upvotes: 0

Views: 450

Answers (2)

andy
andy

Reputation: 21

If you are considering to put the Load of 1000 users, you can run the test in the distributed mode, refer to the link for details https://jmeter.apache.org/usermanual/jmeter_distributed_testing_step_by_step.pdf

Upvotes: 1

Dmitri T
Dmitri T

Reputation: 168072

If you need to test your system at 3500 requests per second you need to use slightly different approach, to wit add Constant Throughput Timer to your Test Plan and configure it to limit JMeter requests rate

JMeter Constant Throughput Timer

However from what I can see from your Summary Report the majority of samplers are executed at rate of 3 requests per second and it have to be at least 58 requests per second in order to achieve 3500 requests per minute. So most probably your application simply cannot handle the load.

I would recommend first of all checking out whether your application has enough headroom to operate in terms of CPU, RAM, Network, Disk, Swap, etc. You can use i.e. JMeter PerfMon Plugin.

Also make sure that JMeter itself can produce the required load, default JMeter configuration might be not suitable for conducting the load of 1000 concurrent users so make sure you follow JMeter Best Practices, especially:

  • Run your test in non-GUI mode
  • Disable all the Listeners
  • Increase JMeter HEAP size as by defaults it's only 1 GB which might be not enough.

Upvotes: 1

Related Questions