Hubbry Logo
search button
Sign in
Web server benchmarking
Web server benchmarking
Comunity Hub
History
arrow-down
starMore
arrow-down
bob

Bob

Have a question related to this hub?

bob

Alice

Got something to say related to this hub?
Share it here.

#general is a chat channel to discuss anything related to the hub.
Hubbry Logo
search button
Sign in
Web server benchmarking
Community hub for the Wikipedia article
logoWikipedian hub
Welcome to the community hub built on top of the Web server benchmarking Wikipedia article. Here, you can discuss, collect, and organize anything related to Web server benchmarking. The purpose of the hub...
Add your contribution
Web server benchmarking

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]