Long running routine x time out

[RSLyra]

I had two long running routines. One recover data from 500 public servants, the other many government pages to verify which one is using CMS.

Until last December, everything was allwright. But I decided to change the host, and then I got this:

"Gateway Timeout
The gateway did not receive a timely response from the upstream server or application."

I don't want to come back to my old host, and the new one said that I need to change to a bigger and expensive plan to change settings like timeout, waht is not a option either.

I tried flush() and ob_flush(), nothing changed.

[Webdongle]

You get what you pay for

[RSLyra]

Thanks. Very helpfull.

[ranwilli]

Talk to your host...

[toivo]

You can use the sleep() function every now and then in your script to give slices of CPU time to other processes.

Ref. http://php.net/manual/en/function.sleep.php

[RSLyra]

Hi Toivo.

My problem is to not publish anything in a long time, so I got a Timeout.

So, sleep() is not the point.

And memory don't look to be the problem.

Tahnks

[toivo]

If your script takes a long time to run in general, the sleep() function effectively prevents timeouts caused by the script exceeding the processing time limit in PHP, set by the directive max_execution_time in php.ini, over which you do not have any control in a shared server environment.

On the other hand, if your script has to wait for a response from another server and the response takes a long time or never arrives, it is up to the developer to configure the call making the request with proper timeouts and then do the error handling, including retries, where the sleep() function could also be useful.

[RSLyra]

"another server response" is just the case.

I scrap site to get information. One routine collect information about 500 public servants. The other open 1600 government sites (pages) to check if they are using some kind of CMS.

[RSLyra]

But I will do a small test with sleep().

[RSLyra]

Sleep didn't work.