How to tune nginx for 800-1200 concurrent connections?

[li zJay]

I think the bottleneck may be the PHP, it is a piece of cake for ngx to
handle 1k concurrent connections  without any special tuning.

On Tue, Sep 20, 2011 at 4:40 AM, John Joseph Bachir <j at jjb.cc> wrote:

> * might consider turning up keepalive to 65
> * depending on the nature of your content you might want to turn up when it
> expires -- example: expires 10m;
> * looks like you have 2 workers per core -- typically a worker process per
> core is recommended (or maybe your have intel cores with "hyerthreding", in
> which case maybe 8 is the more relevant #
>  * what's your cpu load like? is your server cpu-bound or is IO the
> problem? if you can find some way to do fewer disk reads and more ram reads
> that will help
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>



--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20110920/21899ac3/attachment.html>