<a href="http://drupal.org/project/job_queue">http://drupal.org/project/job_queue</a> I use it all of the time and it works great. Sometimes I will make a custom module with a system weight lower then job_queue and ini_set... in hook_cron to increase a timeout if needed.<div>
<br></div><div>Cheers,</div><div>Neil<br><br><div class="gmail_quote">On Thu, Jul 15, 2010 at 9:11 AM, Ken Winters <span dir="ltr"><<a href="mailto:kwinters@coalmarch.com">kwinters@coalmarch.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">unset() and paging your batch chunks with LIMIT are the standard strategies if<br>
you wrote the cron yourself.<br>
<br>
You might also be able to use ini_set('memory_limit','200M'); but actually using<br>
less memory is generally preferable.<br><font color="#888888">
<br>
- Ken Winters</font><div><div></div><div class="h5"><br>
<br>
On Jul 15, 2010, at 9:04 AM, Ken Rickard wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Drush scripts (especially bulk node processing) are subject to hitting<br>
PHP memory limits when processing large amounts of data.<br>
<br>
Anyone have ways around that issue?<br>
<br>
On Thu, Jul 15, 2010 at 8:49 AM, Moshe Weitzman <<a href="mailto:weitzman@tejasa.com" target="_blank">weitzman@tejasa.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think drush scripts are your best bet. CLI PHP is not not subject to timeout.<br>
<br>
On Thu, Jul 15, 2010 at 5:01 AM, Sven Decabooter <<a href="mailto:sdecabooter@gmail.com" target="_blank">sdecabooter@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
I'm reading contradicting posts about running Batch API processes on cron.<br>
This is for Drupal 6 BTW.<br>
I have tried implementing a batch functionality that should be run on cron,<br>
but it doesn't seem to process the work that needs to be done.<br>
I assume this is because running the cron through a commandline command<br>
doesn't allow for javascript...<br>
So my questions:<br>
- Have I implemented Batch API incorrectly, and should it normally work also<br>
on cron?<br>
- What is the best way to run a process that would normally trigger a php<br>
script timeout? Can I use the Queue module for that?<br>
I'm sure plenty of people have already tried doing this, so I'm not sure why<br>
I can find little consistent information about it.<br>
Thanks for your feedback.<br>
Sven<br>
</blockquote>
<br>
</blockquote>
<br>
<br>
<br>
-- <br>
Ken Rickard<br>
<a href="mailto:agentrickard@gmail.com" target="_blank">agentrickard@gmail.com</a><br>
<a href="http://ken.therickards.com" target="_blank">http://ken.therickards.com</a><br>
</blockquote>
<br>
</div></div></blockquote></div><br></div>