> From: Martin Gainty [mailto:mgai...@hotmail.com]
> Apache is hamstrung by the number of prefork processes it can spawn..
Yes. For this job, it's hamstrung by the PHP process being single-threaded and
therefore having to spawn and keep multiple copies (each with its own address
space) to handle concurrent requests.
In other words: PHP (at least up to PHP5) is architecturally unsuitable for
high-throughput services. It can be made to work, as Facebook demonstrates;
but there are better architectures that have lower overhead.
Actually, that's an interesting question. I wonder how many tonnes of carbon
would be saved per annum if Facebook were reimplemented in something that
allowed multiple threading and smaller sessions, such as Mono/ASP.Net or
glassfish/servlets? <ducks and runs to avoid the PHP lynch mob>
- Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
