Am 12.10.2013 17:45, schrieb Martin Nowak:

On Sun, 29 Sep 2013 10:21:46 GMT, Dicebot wrote:

On Sat, 28 Sep 2013 20:56:22 GMT, Martin Nowak wrote:

I reach about 4000 req/s.

Without keep-alive that was.

P.S. I got at most ~ 18 000 req/s with -c 2500 when testing about half an year ago and then it was network card bottleneck, not application.

But 2500 connections is somewhat irrelevant for HTTP.
After fixing the keep-alive issue I also reach
around 18k req/s with less then 10 connections. This is for a simple hello world plaintext response, rendering pages still shows up with quite some GC in the profiler.

To reach full speed you also need to add
-version=VibeManualMemoryManagement (makes it unsafe to escape data from
HTTPServerRequest).

I reached about 90 kreq/s using "weighttp -c 100 -k -n 100000" some time
back when Dicebot did his first benchmark tests. That was using a
standard desktop as the server (AMD Phenom2) and a laptop (Core2Duo)
over a GbE connection. The bottleneck still was the client in this setup.

That was some time ago though, so there may be some more performance
regressions by now. I'll add a CI based performance test in a while to
stabilize performance over time.