Editing Web server (section)

=== Performance metrics ===
For web server software, main key '''performance metrics''' (measured under vary [[#Operating conditions|operating conditions]]) usually are at least the following ones (i.e.):<ref name="first-monday-web-server-performance">{{Cite journal|url=https://firstmonday.org/ojs/index.php/fm/article/view/539/460|title=WebMonitor: a tool for measuring World Wide Web server performance|author1=Jussara M. Almeida|author1-link=Jussara M. Almeida|author2=Virgilio Almeida|author3=David J. Yates|journal=First Monday|date=1997-07-07|doi=10.5210/fm.v2i7.539|access-date=2021-11-04|language=en|archive-date=4 November 2021|archive-url=https://web.archive.org/web/20211104215116/https://firstmonday.org/ojs/index.php/fm/article/view/539/460|url-status=live |doi-access= free}}</ref>

* {{strong|number of ''{{visible anchor|requests per second}}''}} ({{strong|RPS}}, similar to {{strong|[[queries per second|QPS]]}}, depending on HTTP version and configuration, type of HTTP requests and other operating conditions);
* {{strong|number of ''connections per second''}} ({{strong|CPS}}), is the number of connections per second accepted by web server (useful when using HTTP/1.0 or HTTP/1.1 with a very low limit of requests / responses per connection, i.e. 1 .. 20);
* {{strong|[[network latency]]}} + '''[[Response time (technology)|response time]]''' for each new client request; usually benchmark tool shows how many requests have been satisfied within a scale of time laps (e.g. within 1ms, 3ms, 5ms, 10ms, 20ms, 30ms, 40ms) and / or the shortest, the average and the longest response time;
* {{strong|[[throughput]] of responses}}, in bytes per second.

Among the operating conditions, the {{strong|number}} (1 .. ''n'') of {{strong|concurrent client connections}} used during a test is an important parameter because it allows to correlate the {{strong|[[Concurrency (computer science)|concurrency]] level}} supported by web server with results of the tested performance metrics.