Topic: PHP5Apache2_4 Version

[gdprogrammer59]

I have downloaded the most current versions of Apache 2.4.1 (OpenSSL 1.0 and 0.9.8t and APR 1.4.1 and APR 1.4.5).

The first question is I that Apache shows Apache 2.4.1 (Win32) OpenSSL/0.9.8t PHP/5.4.0RC7. I am using PHP 5.4RC8 - does the php5apache2_4.dll need to be updated and/or back up to PHP 5.4.0RC7?

The second question is that I prefer to use the php5apache2_x.dll instead of Fast CGI (perhaps silly reasons dating back to IIS 5/6/7 and PHP). The question is which (the DLL or Fast CGI) the better method to interface between Apache and PHP (with better being more reliable and performance)?

Thank you!

[Steffen]

The handler is build against RC7, no problem with RC8, because no API changes. When PHP 5.4 is final then I build it against it.

The second question can better be answered by James Blond


Steffen

[James Blond]

Steffen, I wonder why you didn't answer that question.

PHP as module is might be a bit faster than the fcgid one. So in theory. I haven't noticed a difference yet. The advantage of using Fast cgi is the separation of apache and PHP. Than the memory usage of Apache itself is a lower. The memory usage overall (httpd.exe and the instaces of php-cgi.exe) is the same than running apache with PHP as module. Might be a little overhead. The advantage is that when you use unstable 3rd party extension / modules in PHP apache won't crash only a single instance of PHP cgi process.
Under huge amount of requests you need 2 or more cores when using mod_fcgid to have the full advantage.

You also can run mod_fcgid and php as module parallel for testing. Steffen knows how to do that

[gdprogrammer59]

Thank you for the responses!

The question about FastCGI versus module stems from a comment about a huge number of requests and 2 or more cores.

When you say "huge number of requests" what kind of numbers are you referring to?

Is it only the FastCGI that would utilize multiple cores (i.e. would the module utilize multiple cores) and is there any requirements from a configuration file to allow Apache to use the additional cores?

Thank you!

[James Blond]

With a "huge number of requests" I mean more than 200 requests per second. But I had site with more requests on a page with single core CPU, but the execution didn't take long, under 10 ms per request and that also worked fine.
I don't know how apache uses the cores. There are two processes and more threads. I don't know how apache spreads these threads. That might answer some other.