Brian Akins writes:
Colm MacCarthaigh wrote:
I've never put a worker Apache into production because most of our
systems depend on PHP or something else which I wouldn't trust 100% in a
threaded configuration.
Is there anything we can do in 2.4/3.0 that will help gain that trust?
PHP, or it's extensions or whatever they call them, are not thread safe.
So until that's fixed, nothing we can do. Probably the same with other
stuff.
worker wokrs for me, though.
--
Brian Akins
Lead Systems Engineer
CNN Internet Technologies
Exactly. I run a website for a former employer which still gets
considerable traffic in terms of downloads of large files and runs a
medium-to-heavy use forum system based on PHP. Multiple sites built with
the LAMP stack (P being PHP in this case, although there is some PERL
backend).
Right now, in order to keep from bogging a particular server down with
latent or slow connections, I have had to impliment a load balanced
configuration with multiple servers in a case where one or two could easily
suffice if I could trust a multi-threaded model.
We have actually discussed this a couple other times on the list. There is
(at the very least) a percieved slowness in migration to the 2.0 apache
setup and indeed slower to multi-threaded MPMs, even in situations that
would absolutely benefit from them. Why? PHP is one of the biggest reasons
I have been hearing from colleagues.
Has any kind of extensive testing been done against a multi-threaded
implementation of a PHP-based testing sled to find out what (if anything) is
breaking in a threaded environment? Do we have hard data to offer the PHP
community to encourage additional specific work and move towards thread-safe
"certification" of some of the underlying PHP core and modules?
-----------------
Wayne S. Frazee
"Any sufficiently developed bug is indistinguishable from a feature."
