On 27/09/12 17:40, Marten Lehmann wrote:
A point that I don't find optimal with FastCGI for shared hosting user
monitoring is, that as a sysadmin or user you typically can't tell
which script is actually been executed by a FastCGI worker, so all you
can tell the user is "some PHP script in your account creates very
high load".
Also, dynamically spawning additional workers wih PHP-FPM is great,
but at least the first one has to run forever, probably doesn't free
previously allocated memory and one shared hosting server with 16 and
more CPU cores usually manages several hundrets of web accounts. And
this has to be multiplied with the numbers of PHP versions you
support. For now this is the latest release for each of PHP 4.4, PHP
5.2 and PHP 5.3, PHP 5.4 will be added soon. Since PHP 5.2 breaks the
register_global default of PHP 4.4 and the PHP 5.3 ZendGuard is
incompatible with the PHP 5.2 ZendOptimizer bytecode, we have to keep
all of those releases in parallel to not break any application.
So I guess, having a dedicated VM with only one PHP version can be
seen as a privilege for a small minority of PHP users.
Yup, only the likes of GoDaddy et al host 1000's of accounts per server,
but you're right that most offer some or all of the PHP versions 4.4,
5.2, 5.3 and 5.4 in php-cgi mode and some an optional php-fpm at 5.2. I
suspect that many if not most users have still to move to 5.3 because of
PHP version dependency issues. I've been burnt by that one myself.
