Scalability issue

Maxim Dounin mdounin at
Tue Mar 24 20:56:42 MSK 2009


On Wed, Mar 25, 2009 at 01:12:29AM +0800, howard chen wrote:

> Hey
> I am new to nginx.
> According to the web:
> It said...
> Nginx is one of a handful of servers written to address the C10K
> problem. Unlike traditional servers, Nginx doesn't rely on threads to
> handle requests. Instead it uses a much more scalable event-driven
> (asynchronous) architecture. This architecture uses small, but most
> importantly, predictable amounts of memory under load...
> But my questions are...
> 1. No matter how fast you are delivering the data, it is bounded by
> only one thread, so it is not scalable as nowsaday if you have 8 core
> + server?

No.  You just configure nginx to run 8 worker processes - and this 
effectively uses all available CPU resources with minimal 

> 2. Even you are using event-driven, remote clients must also need to
> establish a remote port to your web server, so you can't save much
> resources in fact?

Yes, you can't save sockets.  No, there is a lot of resources that 
saved in fact compared to thread-per-connection or 
process-per-connection models, since thread is much more than 

Maxim Dounin

More information about the nginx mailing list