are you running php4isapi.dll (ISAPI) or php.exe (CGI) version? I know people recommend CGI, but post 4.2.3, the ISAPI version is very stable and you'd be nuts to run a busy site in CGI mode.
If you're running CGI, here is an explanation: The most expensive operation is the *connection*, why mysql gets flogged is because every time you close down a php script, it dies and the connection dies, so a new one needs to be re-established. It can take only 10-20 concurrent connections to kill the server. To "fix" this (it's more an infrastructure issue, really): 1) run ISAPI version of php 2) under [MySql] in php.ini, make sure mysql.allow_persistent = On You'll be amazed at the difference. "Gary Broughton" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I wonder if anyone could offer any advice. We have a series of message > boards using a MySQL database running under ASP on Windows 2000 IIS 5 fine. > Today I put the a PHP version live after it had been tested over the weekend > with about 20 users. As soon as I enabled PHP on the live website (separate > to the test PHP already running), the CPU usage for MySQL-nt went up to 100% > constantly, making the site run at a crawl. After uninstalling PHP and > reverting to the ASP version for the live site, it all ran smoothly again. > I have the Application set to Low (IIS Process) on both sites, the > cgi.force_redirect is 0 as required, and the machine is a dual 1.8G Pentium > with 512MB of memory (I know this could do with doubling, but why is it okay > running ASP code?). I've scoured the net looking for any suggestions, but > without coming across anything concrete. Has anyone any ideas I could try > out at all? > Many thanks > Gary Broughton > > -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
