optimization guidelines...
Ilan Berkner
iberkner at gmail.com
Wed Jan 14 20:06:58 MSK 2009
Thanks for the advice, I will research.
On Wed, Jan 14, 2009 at 11:56 AM, Olivier Bonvalet <nginx.list at daevel.fr>wrote:
> Hello,
>
> 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,
> Olivier
>
> 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).
>> Thanks
>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20090114/a6afc7df/attachment.html>
More information about the nginx
mailing list