On Jul 7, 2009, at 10:17 AM, Graham Leggett wrote:
Paul Querna wrote:
It breaks the 1:1: connection mapping to thread (or process) model
which is critical to low memory footprint, with thousands of
connections, maybe I'm just insane, but all of the servers taking
market share, like lighttpd, nginx, etc, all use this model.
It also prevents all variations of the slowaris stupidity, because
its
damn hard to overwhelm the actual connection processing if its all
async, and doesn't block a worker.
But as you've pointed out, it makes our heads bleed, and locks slow
us down.
At the lowest level, the event loop should be completely async, and be
capable of supporting an arbitrary (probably very high) number of
concurrent connections.
We are looking at a kernel-like scheduler more than anything
else...
