Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21b326ba989c6fa

Jump to content

Web server benchmarking

From Wikipedia, the free encyclopedia

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

Key parameters

[edit]

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.

Tools for benchmarking

[edit]

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


Web application benchmarks

[edit]

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.

References

[edit]
  1. "WRK - a HTTP benchmarking tool". GitHub. 28 May 2022.
  2. "Open source load testing tool review 2020". k6.io. Retrieved 2023-06-02.
[edit]