Performance testing for large size web-services -Mayank Gupta -Devika Hans

Abstract: To maximize web performance requires end-to-end optimization – bandwidth, load balancing, application code, databases, user connectivity, configuration settings, shared environments.

Performance testing It is the testing which is performed to ascertain how the components of a system are performing under a particular given situation. Resource usage, scalability, and reliability of the product are also validated under this testing. It is the superset for both load & stress testing. The primary goal of performance testing includes establishing the benchmark behavior of the system.

Performance testing

Performance testing (Goals): The benchmark and standard of the application should be set in terms of attributes like speed, response time, throughput, resource usage, and stability. All these attributes are tested in a performance test. It does not aim to find defects in the application.

Load testing: Load testing is meant to test the system through constantly and steadily increasing the load on the system until it reaches the threshold limit. Determine how many request your web-service can handle.

Load testing (goals): Exposing the defects in application related to buffer overflow, memory leaks and mismanagement of memory. The issues that would eventually come out as the result of load testing may include load balancing problems, bandwidth issues, the capacity of the existing system, etc. To determines the upper limit of all the components of application like a database, hardware, network, etc. so that the application can manage the anticipated load in future. To set the SLAs for the application.

Stress Testing: Various activities to overload the existing resources with excess jobs are carried out in an attempt to break the system down. Negative testing, which includes removal of the components from the system is also done as a part of stress testing. (chaos-monkey) Stress testing evaluates the behavior of the application beyond peak load and normal conditions. The purpose of stress testing is to ascertain the failure of the system and to monitor how the system recovers back gracefully.

Stress Testing (goals):  Post-crash reports to define the behavior of application after failure. Ensure that the system does not compromise the security of sensitive data after the failure. The system will come back to normality along with all its components even after the most terrible breakdown.

How to configure? Load pattern: Auto Scaling service: Phase roll-out On different endpoint Different geography. Spikes Auto Scaling service: Up scaling policies. Down scaling policies. Auto scaling parameters. Phase roll-out Input data variations

Performance testing tools: Load runner Apache JMeter LoadUI NG Pro CloudTest Httperf

CloudTest: SOASTA CloudTest is a performance testing tool for web sites, mobile apps, APIs, and more. This CloudTest has the capacity to enable number of users to use the website at the same time. Multi-geo support. The trial version with power of 100 concurrent users is available for free.

CloudTest:

CloudTest:

CloudTest:

CloudTest:

References: https://en.wikipedia.org/wiki/API_testing http://testng.org/doc/ https://jenkins.io/doc/

Author Biography Mayank Gupta: I am working with Adobe from last 5 years as a Software engineer. In Adobe I have worked on Adobe AIR, Adobe reader on android, Flash Runtime, Project 1324 and Creative cloud services. I have completed my B.Tech from M.B.M. engineering collage, Jodhpur. Devika Hans: I am working with Adobe from last 9 months as a Software engineer. I have worked on Creative cloud services here. Prior to this I have worked with Infosys for around 2.5 years. In Infosys, I have worked on development and maintenance of REST services. I have completed my B.Tech from GGSIP University.

Thank You..!