mike503 at gmail.com
Wed Jan 14 21:58:50 MSK 2009
Php-fpm handles the children automatically. No need for the
On Jan 14, 2009, at 9:06 AM, "Ilan Berkner" <iberkner at gmail.com> wrote:
> Thanks for the advice, I will research.
> On Wed, Jan 14, 2009 at 11:56 AM, Olivier Bonvalet <nginx.list at daevel.fr
> > wrote:
> if you use a wrapper for PHP with for exemple "export
> PHP_FCGI_CHILDREN=16", then the opcode cache will be shared between
> 16 php instances.
> If you have 4 or more CPU, you should try to use "xcache" instead of
> "apc" (and don't forget to adjust the xcache.count parameter), which
> give much better results for us (about 75% faster in high load).
> Good luck,
> Joe Aston a écrit :
> I seem to remember using PHP APC with FastCGI was a bad idea because
> php-cgi processes couldn't share the same cache - they all required
> their own unique caches.
> How many php-cgi processes are you running?
> On Wed, Jan 14, 2009 at 4:14 PM, Ilan Berkner <iberkner at gmail.com <mailto:iberkner at gmail.com
> >> wrote:
> Does anyone have specific or "generic" optimization guidelines for
> running Nginx in the following configuraiton?
> - Dedicated Nginx server (1)
> - PHP FPM
> - FastCgi
> - Dedicated DB Server
> - MySQL
> Traffic on our site is increasing and I noticed that CPU
> utilization on our Nginx server is going over 50%, primarily to
> php-cgi processes. We are optimizing php using APC.
> Any suggestions would be greatly appreciated (additional
> information can be provided).
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx