Web server benchmarking is the process of estimating a web server performance in order to find if the server can serve sufficiently high workload.

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages) This article needs additional citations for verification. (May 2022) The topic of this article may not meet Wikipedia's general notability guideline. (June 2023)

The performance is usually measured in terms of:

• Number of requests that can be served per second (depending on the type of request, etc.);
• Latency response time in milliseconds for each new connection or request;
• Throughput in bytes per second (depending on file size, cached or not cached content, available network bandwidth, etc.).

The measurements must be performed under a varying load of clients and requests per client.

Load testing (stress/performance testing) a web server can be performed using automation/analysis tools such as:

• Apache JMeter, an open-source Java load testing tool
• ApacheBench (or ab), a command line program bundled with Apache HTTP Server
• Siege, an open-source web-server load testing and benchmarking tool
• Wrk, an open-source C load testing tool^[1]
• Locust, an open-source Python load testing tool^[2]

Web application benchmarks measure the performance of application servers and database servers used to host web applications. TPC-W was a common benchmark emulating an online bookstore with synthetic workload generation.