As per discussion with darthsteven on IRC:

<mcdruid> darthsteven: I've a problem with views_data_export and batch export via drush - in that drush is running out of memory (with 128mb)
 it actually managed to spit out the export before dying, which was very noble
<NikLP> batch?
<mcdruid> but I thought that was not supposed to happen when batched
<darthsteven> mcdruid: drush runs its batches in a single process, so you can very easily run out of memory
<mcdruid> unless I'm missing something, it is set up to use batched export - if I visit the path in the browser I get a batched job
<darthsteven> mcdruid: if you open an issue, a feature request to process the batch in different processes, we should be able to do it
<mcdruid> darthsteven: ah ok, thanks - so is there a solution other than... right ok
<mcdruid> darthsteven: thanks very much (may have to throw more memory at it in the meantime)
<darthsteven> mcdruid: We're just using drush's implementation of batch API, which is a bit naive

Thanks!

Comments

mcdruid’s picture

Issue summary: View changes

added code tags to format copy-and-paste from IRC

greggadsdon’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)

As Drupal 6 nears the end of its life and support period, the 6.x version of Views Data Export will not be supported either. To that end, this issue has been closed, and will not be resolved in the 6.x branch of Views Data Export.

If this issue is still relevant to 7.x branch of Views Data Export, then please re-open and move to a relevant 7.x version.