Hi jerome<br>All your points duly noted. :)<br><br>Revising all again... <br>
<b>worker_connections = 2048 <br></b>I have its value 1024 (nginx default I guess)<br>I have one very important question here.<br>When we say server load - we mean number of HTTP requests. right?<br>Number of unique pageviews and other sweet number shown by Google Analytic wont be helpful, atleast directly.<br>
<br>Is setting up this number very high - like 20480 can adversely affect a high traffic server?<br><br>>worker_process = num of CPU. nothing more<br>I will make this a law for myself. :)<br><br>>you can save more of OS as there is file caching which is useful<br>
By file caching do u mean php cache which stores page output in html files and then serve them via nginx rewrites.<br>Like wp-super-cache in wordpress world.<br>By the way I have memcached + APC + CDN + wp-super-cache and now exploring fastcgi_cahce by nginx.<br>
<br>I am just obsessed with performance.<br>And I am really not doing this to save my hosting bill.<br>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!<br>
<br>>a dynamic content nginx is serving from cache won't generate any load<br>
>on the fcgi side as it won't go there<br>This sounds nice. <br>Surprisingly I haven't seen more about it?<br><br>-Rahul<br>