BatchJobService recommendations

[GregT]

Hi,

We've been using the MutateJobService (and its precursor) successfully for years, and have to update to the BatchJobService as the last version that supports MutateJobService is sunsetting soon. I have a couple questions regarding this:

1 - On the official blog, one of the benefits listed for the new service is it supports potentially hundreds of thousands of operations per batch (as opposed to the max of 10k, if I remember right, for MutateJobService). The batch processing guide says you should do a few large jobs rather than lots of smaller jobs. So, for things like changing keyword bids and mobile/audience bid modifiers, do you have a recommendation on the number of operations to use? Is 100k a reasonable amount, or even 500k or 1M? We have a number of clients where we need to send 1 to 1.5 million of these at a time, if that matters.

2 - The design of the upload of the operations seems to be well suited to handling large jobs, because you can break things into reasonable sized chunks and upload them separately into the same job (so all operations don't have to be in memory at once). Looking at the Java SDK, it doesn't appear, though, that there is similar functionality for the downloading of the results - i.e. it appears the only option the Java API SDK gives you is to download all the results into memory at once. Is that correct? Just want to be sure I'm not missing anything.

Thanks in advance,

Greg

[Vishal Vinayak (Adwords API Team)]

Hi Greg, 

1) An AdWords account has a hard limit of 1 GB of uploaded operations across all of its batch jobs. I would recommend trying ~500K at a time using the test accounts and if that throws an error, reducing the load and trying again. 

2) While downloading the results using the downloadUrl, the only option available is to download all results at once.

 

Hope this helps! Please feel free to revert in case you have more questions. 

Regards,

Vishal, AdWords API Team

[GregT]

Ok, thanks for the response, Vishal.