[AWS] Having more then 1000 concurrent connections?

[Dennison, Ted]

> Pascal Obry wrote:
> 
> Le 25/08/2011 00:35, Zhu Qun-Ying a écrit :
> > now. Having a task per request looks nice on design but have serious
> > scaling problem on real world for a busy server (lots of
> > request/response).  All the common used web servers (nginx, lighttpd,
> > Apache, etc) do not use this method.
> 
> That's not the design. And some benchmarking have proved AWS very fast.
> There is a pool of task (statically set during initialization) handling
> all requests waiting in a queue.

To be fair, he didn't say it wasn't fast. He said it wouldn't scale.

Logically, you'd think there would be a point somewhere (1,000?, 100,000? 1 Million?) where creating more tasks starts to bog down the CPU a bit. Perhaps that isn't true?