Load testing of Web sites

Daniel A. Menascé

IEEE Internet Computing · 2002 · 136 citations · 2 references

Concepts

TL;DR

Developers assess a Web application's quality of service through response time, throughput, and availability, noting that poor QoS frustrates customers and drives business loss while infrastructure costs rise with expected traffic and upgrades should target bottlenecks such as databases or load balancers. The study aims to guide optimal IT infrastructure investment by determining when and how to upgrade resources to maximize ROI, outlining how load testing addresses QoS factors and business needs. Load testing evaluates a Web site's performance under expected workloads by running scripted customer behavior at varying load levels, and the paper details the QoS factors addressed, the testing process, and its alignment with business requirements.

Abstract

Developers typically measure a Web application's quality of service in terms of response time, throughput, and availability. Poor QoS translates into frustrated customers, which can lead to lost business opportunities. At the same time, company expenditures on a Web site's IT infrastructure are a function of the site's expected traffic. Ideally, you want to spend enough, and no more, allocating resources where they will generate the most benefit. For example, you should not upgrade your Web servers if customers experience most delays in the database server or load balancer. Thus, to maximize your ROI, you must determine when and how to upgrade IT infrastructure. One way to assess IT infrastructure performance is through load testing, which lets you assess how your Web site supports its expected workload by running a specified set of scripts that emulate customer behavior at different load levels. I describe the QoS factors load testing addresses, how to conduct load testing, and how it addresses business needs at several requirement levels.

References

2