Performance Testing Metrics and Workload Approach using Jmeter

Types of testing that we perform on application.

1. Load Testing
2. Soak Testing
3. Stress testing

Metrics that we submit to client

1. Application Average Response Time for each activity
2. Application Average throughput.
3. Application standard deviation.
4. Application & Database server Memory usage.
5. Application & Database server CPU usage.
6. Application & Database server I/O usage
7. Application and Database bottleneck points.

Work Load Approach

Several test cycles may be required to obtain the results desired. The following test cycles are intended to serve as a guideline to the different test executions that may be necessary.

1. Obtain a baseline benchmark for 25% users logging into the system over the course of 15 minutes and performing the scenarios

2. Use the results from the first execution to make a guess as to how many users the system might support. One possibility might be to run 1000 different users through the system for one hour, with approximately 50% concurrent users at a time.

3. If the second execution continues to meet the performance goals, then continue to run new tests with increasing quantities of concurrent users by 25% until the performance goals are no longer met. It is desired that one server will support up to 2000 concurrent users.

4. Assuming the maximum capacity is determined; a consistent load test will be run. The consistent load test will use a number of concurrent users equal to 50% of the maximum capacity. This test will run for 2 hours

5. After both the maximum capacity and consistent load tests have been run, create a baseline test that stresses the system without running the maximum system load. The baseline test is recommended to be run at 75% of the maximum capacity for a period of two hours or more based on application usage..

Please let us know any modifications required.