PHP as an Apache module or as a CGI program, which is best?

Posted: Thu Nov 03, 2005 6:32 pm

Hi

I know that php-nuke requires PHP version 4.2.x or better (mod_php) and prefers an Apache module, but what implications are there if your host runs php as a cgi program not an apache module.

I need help in clarifying this as I am in the market for a new host and want to make a informed choice.

Issues when using cgi are (I think):

1) Page loading is slower.
2) Sentinel install problems.

Are there any more issues?
Should I select my hosting provider based on this specification?
or is it not worth worrying about because there are work-arounds?

Regards

Martyn.

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

I would highly recommend Apache as a module. Google for apache cgi vs module and study up on that. As far as a great hosting solution, look no further! Join Raven Web Hosting RavensScripts

Posted: Fri Nov 04, 2005 5:24 am

This is a very debated (and debatable) issue.

There are demonstrated examples of it being better as a CGI and then again, also demonstrated examples of scenarios where it is better as a module.

To quote some info:

Dynamic components are probably the most time-sapping component of any Web server. Dynamic components, especially if you are using CGI, can add seconds to the response time just to load and execute a simple application. A more system options can be found at mod_perl, PHP, and Python, and the Jakarta interface for Java.

The main advantage of the script-based solutions is that they embed the interpreter into the Apache executable, which removes the initial loading problem with dynamic scripts. Some will even cache the parsed script so the next time it's requested it need only to be executed.

Configuration can be complex and getting the exact system correct can be time consuming. Some solutions also don't work quite as one would expect with virtual hosts, and you will need to change certain scripts to take full advantage of the speed enhancements on offer.

The improvements, however, can be significant, with as much as 70 percent of the execution time being knocked off of a Perl script simply by using mod_perl in place of CGI. With even more work, these solutions also allow you to keep persistent connections open to databases or to cache information between requests. This is great for e-commerce sites and also for reducing the overhead of otherwise loading information between requests.

In the PHP World, my experience has been that the performance benefit is no where near 70 percent (probably closer to 10 or 20 at the most) but what is also really important is the version of PHP as well as what optimization tools are employed on top of it. Caching is huge and lets face it, nobody uses it which really stinks. Show me a server with MMCache or even Zend caching, and I'll show you a domain that can really scream performance wise. Yeah, it can make that much of a difference.

Additionally, if you are using an old database, it might not matter anyway only in the sense that if you have a slow DB relationship, PHP processing could be the least of your worries.

Client Joined: Jul 19, 2005 Posts: 68

I just pulled out my IIS server and installed Apache, PHP, MySQL, which is the best conf to us for a nuke site and what modules do i need to install. Its on a local network behind a nat firewall ( ive no intention of allowing public access, i just need a test server )

Posted: Sun May 13, 2007 10:33 am

Start with their default httpd.conf and go from there. Turn register_globals off above all else. If you would like me to send you the one I have customized let me know.

Posted: Sun May 13, 2007 1:50 pm

Thats a great idear, thankyou.