Hi Peter, I've talked with the core engineering team about this, and they will investigate the performance issues you encountered in this scenario. In general the benefits of the BulkMutateJobService are:
* Operations are automatically applied at an optimal rate, avoiding operation rate limit errors. * HTTPS connections to the AdWords servers don't need to remain open while the work is being done. * It's cheaper. Best, - Eric On Nov 30, 7:20 am, Peter Niederwieser <pnied...@gmail.com> wrote: > Eric, > > It was a real account, not the sandbox. AdGroupAdService is much > faster. Since the bulk service does not currently meet either of our > expectations (upload whole campaign in one step, faster upload), we > went back to the conventional services. > > Cheers, > Peter > > On Nov 24, 11:05 pm, AdWords API Advisor > > > > <adwordsapiadvi...@google.com> wrote: > > Hi Peter, > > > Thanks for the feedback on this service. Which environment were you > > making requests against? Out of curiosity, have you tried adding the > > ads using the AdGroupAdService to compare the times? > > > Best, > > - Eric Koleda, AdWords API Team > > > On Nov 24, 5:09 am, Peter Niederwieser <pnied...@gmail.com> wrote: > > > > We've been trying to use the new BulkMutateJobService, but it appears > > > to be extremely slow. Adding 400 text ads in one job consisting of 4 > > > parts took 70 minutes. What could be going wrong here? > > > > Cheers, > > > Peter -- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-...@googlegroups.com. To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en.
