Hi,
I have spent a lot of time last year measuring php performance on
multi-threaded vs single threaded fastcgi.
I had used iplanet web server (instead of apache) for my measurement. Out of
the box single threaded php apps were very close (better) than multi-threaded
versions but when we started o
>From our experience if you wish to serve any kind of PHP apps with
internationalization using the popular GNU gettext system ( and right
now there are many of these) then you must use a non-threaded webserver
engine since GNU gettext library is not yet thread-safe (because GNU
gettext process envi
This is just personal experience and observation but...
We are running Apache Worker with PHP safely by using PHP-FPM rather than via a
shared object, so we don't have to worry about thread safety in the PHP
component but can have apache multithreaded. I realise this isn't actually
multi-threade
Hi All,
I have a few questions about the performance of PHP web applications *under
load* and I would appreciate if there is anyone that would like to share
their experiences in terms of any benchmarks or observations.
*Background Information*
In multi-process environments, such as FastCGI, Apac
