By brashquido on

I upgraded my server from PHP 4.4.7 (using IIS 6, PHP FastCGI, EA) to PHP 5.2.5 (Using IIS 6, ISAPI, EA) over the weekend and have noticed a very significant increase in page loading times. Using PHP 4.4.7 the approx average page generation time for Monday last week was 360ms, and the approx average page generation time for Monday this week using PHP 5.2.5 was nearly 1500ms. Traffic stats are about the same, and nothing else on the server has changed apart from the PHP upgrade. I will break out the devel module tonight to try and track down where the delays are occuring, but I was just wondering if anyone else had experienced such a significant performance degradation from upgrading from PHP4 to PHP5?

⋅ Categories: Drupal 5.x

Comments

trophaeum’s picture

trophaeum commented

not an iis user here however look at the fastcgi stuff that recently appeared for iis, it's a much better choice than isapi as far as stability goes, would also recommend xcache instead of ea personally

brashquido’s picture

brashquido commented

Cheers for the reply. I've done a bit of testing with the new MS FastCGI handler, and while good it doesn't work properly with Drupal when any sort of caching is enabled. Not had a lot of luck with xCache or APC due to their shared memory architecture which relies on additional php-cgi.exe processes being created as child processes of the first php-cgi.exe process. This is not the case with IIS as php-cgi.exe processes are created as children of the W3WP.exe (IIS worker process) which means every time a new php-cgi.exe process is created the APC/xCache cache is cleared which not only means the cache is not effective but really hammers the CPU and memory. Eaccelerator does not share memory between php-cgi.exe processes which results in massive memory usage, but at least you get a half way effective opcode cache.
----------------
Dominic Ryan
www.iis-aid.com