I just ran into this exact problem. I elected to solve it via the D6 backport of drupal_queue/cron (after trying BatchAPI) and am pretty happy with it.
Joe On Jul 15, 2010, at 10:24 AM, Alex Barth wrote: > > 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? > > Again: batching. Even tasks that are run with drush need to be worked off in > chunks. > > PHP's just not made for managing memory. > >> >> On Thu, Jul 15, 2010 at 8:49 AM, Moshe Weitzman <[email protected]> wrote: >>> I think drush scripts are your best bet. CLI PHP is not not subject to >>> timeout. >>> >>> On Thu, Jul 15, 2010 at 5:01 AM, Sven Decabooter <[email protected]> >>> wrote: >>>> Hi, >>>> I'm reading contradicting posts about running Batch API processes on cron. >>>> This is for Drupal 6 BTW. >>>> I have tried implementing a batch functionality that should be run on cron, >>>> 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 >>>> doesn't allow for javascript... >>>> So my questions: >>>> - Have I implemented Batch API incorrectly, and should it normally work >>>> also >>>> on cron? >>>> - What is the best way to run a process that would normally trigger a php >>>> 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 >>>> why >>>> I can find little consistent information about it. >>>> Thanks for your feedback. >>>> Sven >>> >> >> >> >> -- >> Ken Rickard >> [email protected] >> http://ken.therickards.com > > Alex Barth > http://www.developmentseed.org/blog > tel (202) 250-3633 > > > >
