ECONNRESET with concurrency > 5 about loadtest HOT 7 CLOSED

Changed in commit a30dfed; upgrade to version 1.2.3 to use it. I used a max of 1000, because why not.

Anyway, I encourage you to use -k to enable keep alive; tests go smoother and the results are more predictable. It may be more realistic if you have a limited number of clients.

Please reopen if the problem is not solved for you.

from loadtest.

Thanks! I did use keep-alive though, and yet came across this issue.

from loadtest.

With keep-alive we are not using the standard Node.js agent, but agentkeepalive which doesn't even use this parameter. Perhaps the issue is in your own backend, or I'm missing something? Let me know how it goes, I'm quite interested in the outcome.

from loadtest.

Most probably this is because I mixed loadtest with custom request generator making other requests with standard Node.js agent.

from loadtest.

OK. Anyway the change should not hurt anyone so I'll leave it there.

from loadtest.

@trustmaster are you running on windows?
on windows i encountered a tendency that requests get dropped after a while especially when the loadtest and the tested server is running on the same machine.
that issues did not appear on *nix

from loadtest.

@zaphod1984 nope, that was on Linux and Mac OS X.

from loadtest.