Re: asynchronous PHP
- From: Lawrence Krubner <lawrence@xxxxxxxxxxx>
- Date: Mon, 29 Dec 2008 11:17:02 -0500
rf wrote:
Lawrence Krubner wrote:The server I'm working on right now allows PHP scripts to run for 300
seconds.
That's a long time. The out of the box default is 30 seconds.
Sure, but most of the companies I've worked at have used a big number. I haven't yet worked anywhere that left the time limit at the default 30 seconds.
I need to get around that. I'm writing a script that pings
the Google Ajax API. The script is called as a cron job. It needs to
make over 100,000 queries against Google.
Consider set_time_limit.
I don't think there is a value that I could set that could ensure this operation run safely. PHP postpones most memory clean up operations till the script is done running. I'd rather find a way to trigger multiple PHP scripts than try to get one PHP script to do everything that I want.
However don't you think that 100,000 hits against google at once might just be a tad over their TOS limits?
My sense is that most Google mashups make a lot more calls than that. Some of the bigger mashups make several million calls a day. Consider any of these:
http://mashable.com/2008/05/14/17-google-maps-mashups-to-waste-away-your-day/
All the same, I've asked about this issue over on the Google Search API forum.
.
- References:
- asynchronous PHP
- From: Lawrence Krubner
- Re: asynchronous PHP
- From: rf
- asynchronous PHP
- Prev by Date: Re: Strings, arrays and efficiency
- Next by Date: Re: Firebug
- Previous by thread: Re: asynchronous PHP
- Next by thread: Re: asynchronous PHP
- Index(es):
Relevant Pages
|