http://lowlatencyweb.wordpress.com/2012/03/26/500000-request...
So can Google's compute engine on a $10 instance:
https://news.ycombinator.com/item?id=6804897
http://googlecloudplatform.blogspot.ca/2013/11/compute-engin...
http://lowlatencyweb.wordpress.com/2012/03/26/500000-request...
So can Google's compute engine on a $10 instance:
https://news.ycombinator.com/item?id=6804897
http://googlecloudplatform.blogspot.ca/2013/11/compute-engin...
OTOH, the beefiest machine I have access to test it is a 4 year old laptop, not a 24-core Xeon.
Google's Compute Engine test was using 200 virtual servers, but it does include network connectivity. The response body is a single byte. Their blog entry is a celebration of the performance of their load balancer more than a statement about the performance of each VM.
In March, we were able to exceed 1M requests with network connectivity and without pipelining to a single server [1]. Our project is not testing static web servers, so we don't test with plain nginx; but I expect nginx would also exceed 1M RPS in this hardware environment. This was using a server with 40 HT cores and a single-byte response body.
Similarly, a highly tuned web server such as OP's Lwan should be expected to exceed 1M RPS (network-connected) on a 40 HT core server. 1M RPS with small response payloads is fairly easy on modern hardware.
Incidentally, we see 6M+ RPS with pipelining in our Round 9 plaintext results [2].
[1] http://www.techempower.com/blog/2014/03/04/one-million-http-...
[2] http://www.techempower.com/benchmarks/#section=data-r9&hw=pe...
40 million req/sec with Lua
http://highscalability.com/blog/2014/2/13/snabb-switch-skip-...