Stress-testing httperf, siege, apache benchmark, and pronk

[lionet]

Pun intended. Today I am doing totally unscientific (but quite useful) comparison between a few well-known HTTP performance tools.

System: FreeBSD 8.2, x86_84 (L3426, no HT, no TB). Both client and servers were on the same host.

Load generators tested:

• httperf (0.9.0)
  
• siege (2.70)
  
• Apache Benchmark, ab (2.3)
  
• Pronk (git master; ghc 7.0.3)

Server

Comments

[jakobz]

Это пиздец, как фокусы. Вроде понятно что наебывают, но хочется понять где. Я к вам не прошел, но не жалею.

[lionet]

Ничего не понятно из того, что ты написал.

[xana4ok]

in man httperf it's said:
The calls in a burst are
issued as follows: at first, a single call is
issued. Once the reply to this first call has been
fully received, all remaining calls in the burst
are issued concurrently. The concurrent calls are
issued either as pipelined calls on an existing
persistent connection or as individual calls on
separate connections. Whether a persistent
connection is used depends on whether the server
responds to the first call with a reply that
includes a ``Connection: close'' header line. If
such a line is present, separate connections are
used.

so, this should do the trick.
httperf --server=localhost --port=80 --uri=/ --hog --wsess=100,100,0 --burst-length=100

[ext_1496215]

I ran similar tests yesterday and found out that ab and siege perform more or less the same and httperf performance varies a lot depending on the page file size, http://spage.fi/benchmark