Jim wrote: >--with-apache is specific to apache1. you have to use --with-apxs2 to >build against apache2.
Apxs normally builds DSO versions of php. Under apache, DSO stands for Dynamic Shared Object support, and there are some important differences between dso and static compiles, primarily perhaps performance and administration. Statically linking stuff can significantly reduce administration headaches. Let's say you have a 15 server web farm and want to roll out a new, tested combination of Apache/PHP and some other modules. By statically compiling them in, you can reduce the rollout to pretty much one file, the httpd binary. If the directory it is in changes it is not the end of the world. Parallel installs don't have to worry about asymmetric upgrades of shared libs, etc. On a 15 server farm, a 10% performance win equals a server or two. That is $3000-6000 in capital costs, and then another $2,000 in rackspace/power costs. While benchmarks are notoriously hard to get right, why not try a simple ab domain/hello.php comparing static vs DSO compiles? You might see something like a 40% improvement with the static compile. It's a few seconds of compile time for some potential real world savings. Love to see some better numbers on this of course, but in my experience going the static route results in a measurable performance win. As far as I know httpd2 still allows static modules. - August -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
