Problem #2 is that the use of PHP makes each Apache process consume more memory. The process consumes more memory even when it is serving static (non-PHP) files such as a JPG. It would be more efficient to have a pool of small processes serving static files, and some larger processes serving the PHP scripts.
can't think of any other way to solve this problem than what you've done.
I don't think his solution really worked, in fact it makes the problem worse. Compared to a single pool of larger processes serving the PHP scripts, there is also a pool of small apache processes that serve static content with the overhead of proxying requests to php scripts to the other server.
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
