On 01/29/2013 05:18 AM, Pierre Joye wrote: > As far as I remember, we already do that for a couple of web servers. > And in the long run, I will rather tell not to use FastCGI for > dedicated hosting and the likes. That being said, I also met many ISPs > which are not happy with the all-fastcgi, memory usageand performance > were the issues (have to read my backlog for other details :).
Those ISPs are probably stuck in old fastcgi-land and haven't figured out FPM's ondemand pooling. If you idle out the ondemand children somewhat quickly you can support a lot of vhosts without using much memory since each one doesn't need to have a running process. Only hosts actually being accessed will have running processes. -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
