Timeouts in wrk2 response

[hinawatts]

Hi,
Can someone explain when wrk2 reports timeouts in response ?
I am doing performance benchmark of a service, and I see response like below -
Socket errors: connect 0, read 0, write 0, timeout 1139 Requests/sec: 9326.30
As per my understanding 1139 requests are those that reached our service but did not get response from our service within configured timeout(tried configuring timeout to 50s for this run). However, when I see service logs, these requests never reached service.
Please help me understand when are timeouts reported in wrk2.

[ayende]

I'm also seeing something similar.

[anshchauhan]

Same here...

[hinawatts]

After multiple runs and using wrk with different configurations, one conclusion I made is - The timeout requests include requests that kept waiting for connection to your service and since all connections of your service are busy processing requests, the requests got timed out at wrk level.