Question about Siege?

Question

stress testing

Hey! The question is as follows - I am doing load testing of a web server using the Siege utility:
siege my.server.ru -d1 -r10 -c100
During operation, siege displays a bunch of messages:
HTTP / 1.1 200 0.46 secs: 10298 bytes ==> /
But among which periodically flash:
Error: socket: unable to connect sock.c:220: Connection timed out
or
warning: socket: -598608128 select timed out: Connection timed out
As a result of testing, the result is something like this:

Transactions: 949 hits
Availability: 94.90 %
...
Successful transactions: 949
Failed transactions: 51
Longest transaction: 9.87
Shortest transaction: 0.37

I look at the nginx logs on the server - in the logs the entries are exclusively of the following nature:
"GET / HTTP/1.1" 200 10311 "-" "JoeDog/1.00 [en] (X11; I; Siege 2.68)"
Then there are approximately 950 entries per request from Siege with a response code of 200.
What is the actual question. Can anyone tell me what the siege output errors are:
Error: socket: unable to connect sock.c:220: Connection timed out
warning: socket: -598608128 select timed out: Connection timed out
and why are these fail requests not fixed on my server? This siege simply cannot wait for a response to previous requests and considers the call to fail for some time? Or can it be related to a proxy (on the network where my server is located), which, according to some tricky obscure principles, cuts requests, and they simply do not reach nginx?

Answer 1

And the Internet channel is enough to load 100 threads?

Answer 2

These are requests that your server did not respond to (or could not respond intelligibly, but simply did not complete the ACK handshake). In general, if this slips, then the server can not cope.
The second option, of course, is that you do not have enough channel at home (pps limits, speed limits). I have not encountered this, since I always tank from data centers or a home server (there is also an excellent channel).

Answer 3

Everyone, thanks for the help! The problem is solved, and really was in the home channel. Tried from work - everything is OK.