Load-testing webservers tools

Load vs stress: load measures the response time, stress measures the throughput (how much data is being transferred between client and server)

  • ApacheBench single-threaded regardless of the concurrency level (-c)
$ ab -n 100 -c 10 http://www.yahoo.com/
  • Httperf able to test HTTP pipelining workloads
$ httperf --server wailua --port 6800 --num-conns 100 --rate 10 --timeout 1
  • weighttp by lighty, supports multithreading as well as asynchronous i/o using libev for concurrent requests within a single thread
$ weighttp -n 100 -c 10 http://www.yahoo.com/
  • httpress similar to weighttp, also uses libev, but supports SSL, evenly distributes load between threads and promptly timeouts stucked connections
$ httpress -n 10000 -c 100 -t 4 -k http://www.yahoo.com/
  • wrk uses nginx’s http parser, combines a multithreaded with event notification (epoll/kqueue), supports scripting for HTTP request generation/response processing
$ wrk -t12 -c400 -d30s http://www.yahoo.com/

Apache’s AB, Lighttpd’s Weighttp, HTTPerf, and Nginx’s “wrk”
weighttp will work very well until 10,000 clients and wrk, which is slower until that point, works better for further concurrencies until 50,000 (that seems to be its limit on localhost)


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s