siege blocked during under siege

[zhugw]

Recently find access a website a little slow , so I used siege to benchmark a css file of the website,
and siege always blocked in progress e.g

➜  ~ siege -r10 -c1 -b https://foo.bar.com/static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css
** SIEGE 4.0.4
** Preparing 1 concurrent users for battle.
The server is now under siege...
HTTP/1.1 200     1.65 secs: 1347983 bytes ==> GET  /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css
HTTP/1.1 200     1.70 secs: 1347983 bytes ==> GET  /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css
HTTP/1.1 200     2.71 secs: 1347983 bytes ==> GET  /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css
HTTP/1.1 200     2.56 secs: 1347983 bytes ==> GET  /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css

and from Nginx log got the fifth request had finished and took time: 191s

114.249.226.254 - - [21/Mar/2020:11:32:33 +0800] "GET /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css HTTP/1.1" 200 540440 "-" "Mozilla/5.0 (apple-x86_64-darwin18.2.0) Siege/4.0.4" "-" - - - 191.508 -

So why when took time is long, siege is blocked? In this situation does it mean the connection is dead because without setting socket timeout so it is blocked.

Another question:
The Second request took 153s and its status is 200, but why the bytes received is 163608 less than normal 1347983?

HTTP/1.1 200     2.21 secs: 1347983 bytes ==> GET  /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css
HTTP/1.1 200    153.32 secs:  163608 bytes ==> GET  /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css
HTTP/1.1 200     4.35 secs: 1347983 bytes ==> GET  /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css

[JoeDog]

Why would check out version 4.0.4? That's really old. Clone the latest version and try that: git clone https://github.com/JoeDog/siege.git

…

On Fri, Mar 20, 2020 at 11:47 PM zhugw ***@***.***> wrote: Recently find access a website a little slow , so I used siege to benchmark a css file of the website, and siege always blocked in progress e.g ➜ ~ siege -r10 -c1 -b https://foo.bar.com/static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css ** SIEGE 4.0.4 ** Preparing 1 concurrent users for battle. The server is now under siege... HTTP/1.1 200 1.65 secs: 1347983 bytes ==> GET /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css HTTP/1.1 200 1.70 secs: 1347983 bytes ==> GET /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css HTTP/1.1 200 2.71 secs: 1347983 bytes ==> GET /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css HTTP/1.1 200 2.56 secs: 1347983 bytes ==> GET /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css and from Nginx log got the fifth request had finished and took time: 191s 114.249.226.254 - - [21/Mar/2020:11:32:33 +0800] "GET /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css HTTP/1.1" 200 540440 "-" "Mozilla/5.0 (apple-x86_64-darwin18.2.0) Siege/4.0.4" "-" - - - 191.508 - So why when took time is long, siege is blocked? In this situation does it mean the connection is dead because without setting socket timeout so it is blocked. Another question: The Second request took 153s and its status is 200, but why the bytes received is 163608 less than normal 1347983? HTTP/1.1 200 2.21 secs: 1347983 bytes ==> GET /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css HTTP/1.1 200 153.32 secs: 163608 bytes ==> GET /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css HTTP/1.1 200 4.35 secs: 1347983 bytes ==> GET /static/css/app.f11c9c1a52d7a6ad1cd224c73b12c34f.css — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#175>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJRHZTPYZXUWVUXB3E4QLLRIQ2DRANCNFSM4LQYXX7A> .