Brian Pane wrote:
Paul Querna wrote:
Paul Querna wrote: > A thread per-connection that is currently being processed.
Yeah, SEDA's model of processing "stages"--basically a succession of thread pools through
which a request passes, each with a queue in front--looks like a promising way of mixing
event-based and non-event-based processing.
Thread context switches will suck performance out of any SEDA implementation.
If I remember correctly SEDA got around this by passing the thread through if the queue was empty, and batching up requests so that instead
of processing one request in a stage you would handle X at a time.
For sure.
Brian
