Re: Using an APC-lite in a GCI / SuPHP environment

On 09/27/2012 05:02 PM, Marten Lehmann wrote: >> fpm has a scoreboard and it sets the proctitle. > > Sounds good. > >>> 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. >> >> Like I said originally, spawning pools on demand is the only missing >> feature I see. That is orders of magnitude easier to implement than an >> efficient per-request opcode caching solution. > > Yes, and tearing them down after a certain amount of time not used is > missing, too. And handling race conditions like when the daemon is just > about to shutdown and a new request comes in. At least using unix > sockets to manage daemons per user and PHP version makes it easier than > dealing with dozends of TCP/IP ports. > >> So you run an instance for each version. That doesn't seem like much of >> a problem to me. > > And per user. Since no user is allowed to have access to a foreign > account, each daemon has to be started with the linux user of that account. No, like I said, fpm already supports per-user pools. The parent process creates pools of child processes that run as whatever user you configure. -Rasmus