Thanks Reinis.

Regarding...

>> [*] Is it good to make [i]PHP_FCGI_CHILDREN = 1[/i] if I am using APC
>> for PHP opcode caching?

>No.

I read somewhere that 2 PHP processes do not share APC cache. So if I
have 10 PHP_FCGI_CHILDREN - that means 10 times cache size.


On
> I would suggest to give it a try to the new FPM sapi/manager which is now included also in 5.3.x core.

I do not use FPM and I really wonder why it is used?
We can directly use php-fastcgi as mentioned here
http://tomasz.sterna.tv/2009/04/php-fastcgi-with-nginx-on-ubuntu/

Thanks for your time buddy.
If you have more inputs, please share.

-Rahul



On Tue, Jun 15, 2010 at 11:27 PM, Reinis Rozitis <r@roze.lv> wrote:
>>
>> [*] Is it good to make [i]PHP_FCGI_CHILDREN = 1[/i] if I am using APC
>> for PHP opcode caching?
>
> No.
> One child won't do anything good on a multicore box (giving the usuall nature of php scripts - waiting on external resources like DBs etc). Nor it can saturate single cpu (also APC doesnt limit you here in any way).
>
> I would suggest to give it a try to the new FPM sapi/manager which is now included also in 5.3.x core.
> It gives you the ability to dynamically manage a pool of php processes (spawn more php childs if the server gets loaded or kill the unneeded spares). That way you dont need to control any settings from the webservers side.
>
> http://php-fpm.org/
> http://php-fpm.org/download/
>
>
> rr
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx

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