On Sat, 21 Sep 2013 15:50:47 GMT, simendsjo wrote:

Some tests using weighttp shows that is doesn't really work very well when running concurrent requests.

..I've actually never had vibe correctly handling many requests in my tests. 

weighttp -n10000 -c100 -t2 -k http://localhost:8181/

It can run fine a couple of times, and then it breaks.
Weighttp says `error: connect() failed: Cannot assign requested address (99), while vibe says Handling of connection failed: Error writing data to socket. Remote hung up?`.
If I let it rest for some time, it's possible to re-run weighttp without it failing. Running it right after it fails just makes it keep failing.

Another thing.. weighttp reports this `requests: 10000 total, 10000 started, 10000 done, 35 succeeded, 9965 failed, 0 errored` - Any idea what 9965 failed means? 


Another thing is some excessive memory usage. If I keep running the tests, the application uses all of my 8GB without releasing anything back. But this might of course be a bug in my app as I haven't tested a minimal vibe app.

I used to test it up to -c 5000 - GC killed the latency at those rates but it worked with very low fail ration.

Maybe regression :(