Wrong statistics for failed transactions

[danbst]

When running siege localhost I see this output:

** SIEGE 4.0.1
** Preparing 25 concurrent users for battle.
The server is now under siege...
HTTP/1.1 403     0.00 secs:     168 bytes ==> GET  /
HTTP/1.1 403     0.01 secs:     168 bytes ==> GET  /
HTTP/1.1 403     0.00 secs:     168 bytes ==> GET  /
HTTP/1.1 403     0.00 secs:     168 bytes ==> GET  /
HTTP/1.1 403     0.00 secs:     168 bytes ==> GET  /
HTTP/1.1 403     0.01 secs:     168 bytes ==> GET  /
....
^C
Lifting the server siege...
Transactions:                     81 hits
Availability:                 100.00 %
Elapsed time:                   0.67 secs
Data transferred:               0.01 MB
Response time:                  0.00 secs
Transaction rate:             120.90 trans/sec
Throughput:                     0.02 MB/sec
Concurrency:                    0.39
Successful transactions:           0
Failed transactions:               0
Longest transaction:            0.02
Shortest transaction:           0.00

The Failed transactions field shows zero failed transactions, but this is wrong with regard to manual:

         Failed transactions
             The number of times the server responded with a return code >= 400
             plus the sum of all failed socket transactions which includes
             socket timeouts.

Or maybe manual is wrong here?

[JoeDog]

The manual is wrong. HTTP challenges are not considered failures. Is that from the siege manual on the website?

Jeff

On Sat, Apr 23, 2016 at 7:48 AM, Данило Глинський (Danylo Hlynskyi) < notifications@github.com> wrote:

When running siege localhost I see this output:

* SIEGE 4.0.1 * Preparing 25 concurrent users for battle. The server is now under siege... HTTP/1.1 403 0.00 secs: 168 bytes ==> GET / HTTP/1.1 403 0.01 secs: 168 bytes ==> GET / HTTP/1.1 403 0.00 secs: 168 bytes ==> GET / HTTP/1.1 403 0.00 secs: 168 bytes ==> GET / HTTP/1.1 403 0.00 secs: 168 bytes ==> GET / HTTP/1.1 403 0.01 secs: 168 bytes ==> GET / .... ^C Lifting the server siege... Transactions: 81 hits Availability: 100.00 % Elapsed time: 0.67 secs Data transferred: 0.01 MB Response time: 0.00 secs Transaction rate: 120.90 trans/sec Throughput: 0.02 MB/sec Concurrency: 0.39 Successful transactions: 0 Failed transactions: 0 Longest transaction: 0.02 Shortest transaction: 0.00

The Failed transactions field shows zero failed transactions, but this is wrong with regard to manual:

     Failed transactions
         The number of times the server responded with a return code >= 400
         plus the sum of all failed socket transactions which includes
         socket timeouts.

Or maybe manual is wrong here?

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/JoeDog/siege/issues/57

[danbst]

this is in man siege