"The specific domain of this benchmark is, yet again, the PingPong benchmark as used earlier in my Async Socket Benchmark. However, there are some differences:
"We will fire multiple requests over a single connection, when possible, by using a HTTP 1.1 keepalive connection
It is a distributed benchmark with multiple clients
We will use an identical WSGI application for all servers instead of specially crafted code to return the reply
We expect the server to understand our HTTP request and reply with the correct error codes
"This benchmark is a conceptually simple one and you could claim that this is not representable for most common web application which rely heavily on blocking database connections. I agree with that to some extent as this is now mostly the case. However, the push of HTML5’s websockets will provide us with lots of highly interactive web applications that require a lot of concurrent and low latency connections on the server side."
