What Your Company Should Consider When It Comes to Load Testing
June 13, 2016

Sven Hammar
Apica

Businesses use load testing to determine the maximum workload their software operations can handle and how their platform holds up during increased usage. Load testing analyzes the performance, reliability, and capacity of a software implementation on specific hardware, as well as gives companies the ability to identify problems that may arise.

Below are several questions businesses should consider as they prepare to conduct a load test.

What Should Your Company Do Before Getting Started on a Load Test?

Know your application. Development teams should establish performance goals (i.e., every web page should load in under four seconds), and test planners should carefully assess the application — knowing what parts are most often used, how many users visit the application at peak load times, what parts are critical, etc. All of this governs the magnitude of the test.

What Should Your Company Look for When Testing?

“Load curves” are the most valuable metrics when it comes to performance. These measurements examine the performance limit by evaluating response time, capacity, and stability of the web application.

Testing a website, for example, includes things such as measuring the average duration of a user session, the number of successful page calls per second, the percentage of page calls that fail, and the average response time to starting pages. These metrics will give your business the numbers it needs to identify how many users can access your application simultaneously before it encounters performance issues.

Another metric to be aware of is the “point of collapse.” This refers to the amount of work an application can perform before it becomes unresponsive.

Now That Your Company Has Completed a Load Test, What Should You Do?

User experience is extremely important to a business, so having insights to where user experience can be improved is invaluable. The test results will allow your company to look at areas where the application can be enhanced. Test results can assist developers in assessing stability problems, application overload issues, and any others concerns that may arise.

For example, test results that measure long response times could mean there are problems with the database connection pool and the database engine. If developers determine there are no issues with the database, the test implies that the application itself has programming inefficiencies that need to be addressed.

As Your Company Works Through Load Testing, Consider These Design Tips

■ Measure the performance curve based on simultaneous user loads by running the same test and increasing virtual users logarithmically to 50, 100, 500, 1000, 1500, 2000, and so on until you have surpassed the performance goal.

■ Make sure the load tests run a sufficient duration by allowing a minimum of 10 minutes for effective test duration. Calculate ramp-up time vs. load size and total length of the test.

■ Be prepared to break or pause the application during the test. Someone should be on hand to restart the application if it goes down.

■ Make sure the testing system itself does not get overloaded, as this will produce inaccurate tests. Monitor load server CPU.

■ Each virtual user needs its own login credentials for a test, as using the same account many times can produce errors not found in real-world situations.

■ Provide a minimal 100 Mbit/second connection between the testing server and the application server.

■ Work with the system administrator, database administrator, or application developer during the analysis stage for feedback and additional data sources, such as log files and CPU monitoring.

Remember that load testing is critical to any web or mobile application. In today’s fast-paced world, make sure your enterprise has the highest possible web performance.

Sven Hammar is Chief Strategy Officer and Founder of Apica

The Latest

June 20, 2018

The larger the company size, the higher the proportion of low IT performers, according to the State of DevOps: Market Segmentation Report from Puppet, based on the 2017 State of DevOps Survey data ...

June 18, 2018

An overwhelming 83 percent of respondents have concerns about deploying traditional firewalls in the cloud, according to Firewalls and the Cloud, a survey conducted by Barracuda Networks...

June 14, 2018

Despite the vast majority of cloud management decision-makers believing that DevOps and microservice enablement are important, very few believe that their organizations are capable of delivering them today — a gap that is costing the average enterprise $34 million per year, according to new report from the Ponemon Institute ...

June 12, 2018

Dev teams are doing their best to give the customers what they want, but oftentimes find themselves in between a rock and a hard place. Teams are struggling to get up to speed with new tools that are meant to make their lives easier and more realistic to hit deadlines. With spring cleaning season upon us, take time this season to tune up agile processes and continue the work of advancing the shift towards DevOps ...

June 11, 2018

The ability to create a culture of DevOps is critical to any organization's ability to deliver applications and services at a high rate of speed, but can we clearly and concisely answer the question: What exactly is DevOps? Despite the best intentions, some large companies are struggling to understand what DevOps actually is, and what it takes to fully implement its concepts and reap its benefits ...

June 07, 2018

The Twelve-Factor App is a methodology that offers a 12-step best practice approach for developers to apply when building software-as-a-service apps that are both scalable and maintainable in a DevOps world. As software continues to be written and deployed at a faster rate and in the cloud, development teams are finding there is more room for failure and vulnerabilities. This blog series will discuss how to build a Twelve-Factor app securely ...

June 05, 2018

Everyone understands the importance of code quality for applications, particularly when DevOps results in releases becoming faster and faster, reducing the room for error. The same issues increasingly apply to databases, which are a vital part of DevOps workflows. Fail to integrate the database into DevOps and you'll face bottlenecks that slow down your processes and undermine your efforts ...

June 04, 2018

DevOps and security traditionally have been siloed functions and security is often seen as a policing function by DevOps team members. However, more mature business leaders are trying to bridge the gap between the two functions to achieve business excellence. This theme was evident from our recent survey where 39% of respondents cited that DevOps and development teams care greatly about their cybersecurity posture, showing that the silo between security/IT and development teams is diminishing ...

May 31, 2018

DEVOPSdigest asked experts from across the IT industry for their opinions on the top tools to support DevSecOps. Part 5, the last installment, offers some final thoughts about "tools" that are not necessarily technology ...

May 29, 2018

DEVOPSdigest asked experts from across the IT industry for their opinions on the top tools to support DevSecOps. Part 4 covers code and data ...

Share this