Posted by Joshua Ruppert on 07/25/06 20:17

With that said I'm not sure what my problem is. I have a website that
has already been developed running Win2K and PHP 4, that I tried to
switch over to FastCGI. When I did this every thing ran fine for a
while, until we had a spike in traffic. (Since FastCGI was tried we
have moved to Win2K3.)

The root cause of the problems seems to be the response time of the DB
servers but I'm not certain. When the database servers became loaded,
the PHP processes seemed to hang while waiting for the database to
respond. Eventually this effected each of the PHP processes started by
FastCGI, completely taking down the site.

The only way I found to restart the PHP processes is to reboot the
machine, because task manager did let me kill the processes that were
started by FastCGI.

Is there anything that you could see (slow DB connections or otherwise)
that would cause this kind of behavior?

I used the PHPLens.com EasyWindows PHP Installer, but I'm having
trouble finding resources to help me fine tune FastCGI opperation.

Any suggestions are greatly appreciated.


Chung Leong wrote:
> Joshua Ruppert wrote:
> > When I'm using FastCGI do I need to code differently than I do when
> > using regular CGI? Because the PHP.exe processes don't go away do
> > global variables stick around from page request to page request,
> > creating the need for better managment / pooling of DB connections?
> >
> > Josh
>
> There is no difference from a programming standpoint. Global variables
> are destroyed at the end of each request.

[Back to original message]