Largest Use?

Anon

I'm getting ready to undertake a pretty massive operation, and am looking at using PHP for it. My question is this...I have to deal with legacy software that does not allow me to use the typical phtml, php, etc extensions. So I need to make my webserver (Apache 1.3.12 on Linux, with php4 and zend optimizer) parse ALL html if I am going to use PHP.

My question is this. How bad a load am I going to create? How far does this scale up? Is anyone out there using this in a massive load heavy enviroment that can give me ideas on what to expect?

Wasn't sure where else to post this. My apologies if it's an incorrect forum.

Anon

Unless your 'normal' HTML files are huge I wouldnt worry about it too much. If it does cause a problem for you you could write a simple index.php which picks up all requests and knows which files to eval() and which to fpassthru(). A rewrite rule like RewriteRule ^/(.*) /index.php?path=$1 would nicely have index.php catch all.

Anon

Seems like an easy thing to test. Install PHP. Wait until a high-load period -- noon, for instance -- and edit httpd.conf so that .html is parsed. Observe performance. Do apachectl restart. Observe performance again. Restore old configuration, apachectl restart ... it only takes a second to flip from one configuration to another, and you should know immediately whether this is an issue.

Anon

We are using this kind of setup, and the only performance issues that we have are database ones. There doesn't seem to be any problems. It appears that the PHP engine passes the HTML through with little or no delay. We are running on 3.0.12.