ID: 20330 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: IIS related Operating System: Windows 2000 Advanced Server PHP Version: 4.2.3 New Comment:
I've had the same problem. I gave my bug report (#19541) about two months ago without receiving any answer. Anyways, have you made fixes to PHP concerning this bug? I would be more than pleased if this bug was fixed. Previous Comments: ------------------------------------------------------------------------ [2002-11-09 16:59:54] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip FYI: PHP on Windows will never be as stable as PHP on Unices... due to the nature that we don't have access to the source and of course there are just very few developers who are interested in using windows in a production environment to publish their PHP sites. Derick ------------------------------------------------------------------------ [2002-11-09 16:50:54] [EMAIL PROTECTED] System Specifications - System Windows 2000 Advanced Server - IIS5 - tested php 4.06, 4.1.2, 4.2.3 (last version tested 4.2.3) - Dual Pentium IV 1.2 GHz - Database SQL Server 2000 Problems - System runs fine under ISAPI until high load at which point database refuses to connect, or IIS locks, computer requires reboot. Under ISAPI CPU runs at about 60%. - Same code/same system runs fine under CGI but CPU runs at 100%. Memory only at 20-30%, no virtual memory in use, database on seperate server running at 5% CPU. - Individual database connection times are under 2 milliseconds for ISAPI, however under CGI they are about 150-300 milliseconds. When using CGI, there are at least 3 expensive database connections per page (however after 3 connections they seem to be pooled as they are around 2-3 ms) cause page times be at least .5 - .8 seconds per page of PURE database connect time (connect time tends to be 60-80% of page time). - Similar pages running under Linux and FreeBSD show no signs of such problems, same under isapi however as stated above as soon as server load gets above 100-200 page hits per second server problems begin. Many refused http connections, many refused database connections, then server crashes causing machine to need reboot (restarting IIS does not solve the problem), causing VERY pissed off client who now believes that PHP is not an enterprise ready solution and only for home/hobbiest use. - No mention on web site that PHP was not ready for prouduction under IIS/Mssql. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=20330&edit=1
