Hi jerome
All your points duly noted. :)

Revising all again...
*worker_connections = 2048
*I have its value 1024 (nginx default I guess)
I have one very important question here.
When we say server load - we mean number of HTTP requests. right?
Number of unique pageviews and other sweet number shown by Google Analytic
wont be helpful, atleast directly.

Is setting up this number very high - like 20480 can adversely affect a high
traffic server?

>worker_process = num of CPU. nothing more
I will make this a law for myself. :)

>you can save more of OS as there is file caching which is useful
By file caching do u mean php cache which stores page output in html files
and then serve them via nginx rewrites.
Like wp-super-cache in wordpress world.
By the way I have memcached + APC + CDN + wp-super-cache and now exploring
fastcgi_cahce by nginx.

I am just obsessed with performance.
And I am really not doing this to save my hosting bill.
I just want to sustain on single node as long as possible, though some day,
our growth forces us to explore path of load-balancing, proxy servers!

>a dynamic content nginx is serving from cache won't generate any load
>on the fcgi side as it won't go there
This sounds nice.
Surprisingly I haven't seen more about it?

-Rahul
_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx