[development] Batch API on cron
neil.hastings at gmail.com
Thu Jul 15 14:00:44 UTC 2010
http://drupal.org/project/job_queue 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.
On Thu, Jul 15, 2010 at 9:11 AM, Ken Winters <kwinters at coalmarch.com> wrote:
> unset() and paging your batch chunks with LIMIT are the standard strategies
> you wrote the cron yourself.
> You might also be able to use ini_set('memory_limit','200M'); but actually
> less memory is generally preferable.
> - Ken Winters
> On Jul 15, 2010, at 9:04 AM, Ken Rickard wrote:
> Drush scripts (especially bulk node processing) are subject to hitting
>> PHP memory limits when processing large amounts of data.
>> Anyone have ways around that issue?
>> On Thu, Jul 15, 2010 at 8:49 AM, Moshe Weitzman <weitzman at tejasa.com>
>>> I think drush scripts are your best bet. CLI PHP is not not subject to
>>> On Thu, Jul 15, 2010 at 5:01 AM, Sven Decabooter <sdecabooter at gmail.com>
>>>> I'm reading contradicting posts about running Batch API processes on
>>>> This is for Drupal 6 BTW.
>>>> I have tried implementing a batch functionality that should be run on
>>>> but it doesn't seem to process the work that needs to be done.
>>>> I assume this is because running the cron through a commandline command
>>>> So my questions:
>>>> - Have I implemented Batch API incorrectly, and should it normally work
>>>> on cron?
>>>> - What is the best way to run a process that would normally trigger a
>>>> script timeout? Can I use the Queue module for that?
>>>> I'm sure plenty of people have already tried doing this, so I'm not sure
>>>> I can find little consistent information about it.
>>>> Thanks for your feedback.
>> Ken Rickard
>> agentrickard at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development