CODEWITHSUNDEEP
jmeterperformance-testing
Bajrang Badaik
Bajrang Badaik

Reputation: 202

Ideal test duration for Performance Test

I have 5 Scenarios in total, and 70 Users segregated to different Scenarios which runs for around 15 Minutes only with 1 Loop configuration.

Is it ideal test duration to evaluate the realistic Performance results?

Or do I need to adjust with the test duration?

Any suggestion on this is highly appreciated.

Thanks

Upvotes: 0

Views: 1635

Answers (2)

Dmitri T
Dmitri T

Reputation: 168052

It depends on what you're trying to achieve. 70 concurrent users doesn't look like a real "load" to me, moreover given you have only one loop you may run into the situation when some users have already finished executing their scenarios and were shut down and some are still running or even have not yet been started. So I would recommend monitoring the real concurrency using i.e. Active Threads Over Time listener to see how many users were online at the given stage of the test.

Normally the following testing types are conducted:

  • Load testing - putting the system under anticipated load and ensuring that main metrics (i.e. response time and throughput) are matching NFRs or SLAs
  • Soak testing - basically the same as load testing, but it assumes prolonged duration (several hours, overnight or over the weekend). This testing type allows to discover obvious and non-obvious memory leaks
  • Stress testing - starting with anticipated number of users and gradually increasing the load until response time starts exceeding acceptable threshold or errors start occurring (whatever comes the first). If will shed some light on the slowest or most fragile component, to wit the first performance bottleneck

Check out Why ‘Normal’ Load Testing Isn’t Enough article for more information on the aforementioned performance testing types.

No matter which test you're conducting consider increasing (and decreasing) the load gradually, i.e. come up with proper ramp-up (and ramp-down) strategies, this way you will be able to correlate increasing load with i.e. increasing response time

Upvotes: 1

Karim
Karim

Reputation: 1034

Performance Tests in java is a bit tricky, it can vary wildly depending on what other programs are running on the system and what its load is.

In an ideal world, you need to use a dedicated system, if you can't make sure to quit all programs you're running (including the IDE), The Java HotSpot compiler kicks in when it sees a ‘hot spot’ in your code. It is therefore quite common that your code will run faster over time! So, you should adapt and repeat your testing methods, investigate memory and CPU usage.

or even better you can use a profiler. There are plenty around, both free profilers and demos / time-locked trials of commercials strength ones.

Upvotes: 0

Related Questions