[FASTCGI] Long delay *after* PHP processing

Tom Bowden charles_thomas at mac.com
Mon Feb 7 13:44:17 EST 2011

Just off the cuff thoughts on this -- it could be that the webhost  
doesn't want to allocate that much scheduled time to one process that  
is not actively processing on a task.

Two seconds is a long time in computer-world... and granted its the  
same as an alarm and wake-up to process at some future date ... not  
dedicated time to your process... but if I were a webhost as large as  
bluehost i wouldn't want to provide that much 'in-the-future'  
resources to any process.

But.. i dunno.. could be just me.


On Feb 6, 2011, at 3:59 AM, Felix E. Klee wrote:

> On Sat, Feb 5, 2011 at 2:29 PM, Felix E. Klee <felix.klee at inka.de>
> wrote:
>> Eventually, one of the requests will take almost exactly a minute to
>> respond. Yet the PHP script that is executed with FastCGI [1] is dead
>> simple:
>>  <?php sleep(2)
> Just got another reply from Bluehost:
>   "Our fastcgi setup works just fine with sleep, just not with the
>   amount of sleep time you are using in your loop. If you want to run
>   this then you unfortunately will not be able to use php5(fast-cgi)."
> I don't believe that this is true. In fact I was able to reproduce the
> problem with a sleep time of just one second. But if it is true that
> FastCGI on Bluehost has issues with "sleep", what may be the technical
> explanation?
> _______________________________________________
> FastCGI-developers mailing list
> FastCGI-developers at mailman.fastcgi.com
> http://mailman.pins.net/mailman/listinfo.cgi/fastcgi-developers

More information about the FastCGI-developers mailing list