[Python-ideas] An alternate approach to async IO

[Guido van Rossum]

On Tue, Nov 27, 2012 at 4:15 PM, Trent Nelson <trent at snakebite.org> wrote:
>     The rationale for all of this is that this approach should scale
>     better when heavily loaded (i.e. tens of thousands of connections
>     and/or Gb/s traffic).  When you're dealing with that sort of load
>     on a many-core machine (let's say 16+ cores), an interlocked list
>     is going to reduce latency versus 16+ threads constantly vying for
>     the GIL.
>
>     (That's the theory, at least.)

But why would you need 15 cores to shuffle the bytes around when you
have only 1 to run the Python code that responds to those bytes?

-- 
--Guido van Rossum (python.org/~guido)