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

Rasmus, I've dropped the DL off this one as its just really a personal aside. One of the nice things about HP giving my papers when I was ill is that I am now a "gentleman of leisure" in what is euphemistically called "early retirement". Even though I am pretty fit now, I just don't see the need to work 60+ hrs a week shovelling corporate shit. Me now -- I am off to spend a month at my cottage in the old town of a Greek Island (one further out from the one where they shot Mama Mia) with my wife. I'll only have intermittent Internet access as we don't have WiFi at the cottage and 3G is crap on the island, so I've got to drink a half litre of wine at the local taverna to get online. Life's just a bitch. However, I'll take the laptop and work on this when I am not walking, swimming, eating, etc. and need a bit of mental stimulation :-)

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.

Doesn't that imply, that some configuration file needs to be updated and php-fpm reloaded with each user added and removed on the webserver?

Well, yes, but you can reload the config without a restart by sending it a SIGUSR2. But again, if that isn't convenient enough, enhancing it to get its config more dynamically from somewhere is again orders of magnitude easier to do than building a per-request opcode caching solution. Perhaps you should do what I do and subscribe to a shared service offering just to see what the darkside is like. (They start at a few $ per month.) These guys have a multiplier in the 1,000s maybe 10,000s of accounts per server. They rely on the fact that most users will do only a few blog posts per month and host their email from their domain. As to enhancing FPM being orders of magnitude easier, we won't really know until both options have been explored. However, I would be willing to bet a nice bottle of wine on this as an aside.

Anyway thanks for your dialogue. Much appreciated and I'll be back in contact when I've got something meaty and some hard data to discuss. Regards, Terry