Wrk no info on Socket error

[artemik]

Wrk can't benchmark my server - all requests always fall to socket read errors.

1. There should be documentation or output that tells what those socket read, write, connect, timeout errors are exactly.

2. The error was in missing the last \r\n in my HTTP response. But Curl can talk to my server just fine. Can Wrk be also less strict? Also, why Wrk doesn't count the time of failed requests, it's obviously that the latency of those requests is also important.

[lucasrodcosta]

Hi everyone! Is there any update on this?

[rcarmo]

This is still an issue today.

[gulmezmerve]

Still an issue today 2024 :P