Hi, Others on the forum may have additional recommendations, but a good place to start would be our Rate Limits guide <https://developers.google.com/adwords/api/docs/guides/rate-limits#take_control>. Our rate limits aren't published and are subject to change, but if you follow the recommendations in the guide your app should be able to handle rate limit issues gracefully.
Regarding MutateJobService <https://developers.google.com/adwords/api/docs/reference/v201406/MutateJobService>, you should expect a request submitted through that service to take a bit more time than the equivalent synchronous request because MutateJobService is doing considerably more, e.g., 1. Automatically retries failed operations for many transient issues 2. Schedules each job 3. Keeps track of the status of each job 4. May break your list of operations into multiple batches of operations This additional functionality does add some processing time. Also, due to the scheduling aspect, if maximum throughput is your top priority then MutateJobService probably isn't the right choice. Cheers, Josh, AdWords API Team On Friday, August 1, 2014 8:08:08 AM UTC-4, Luca Fiaschi wrote: > > Hi, > I have some general question about scalability for an infrastructure that > we are currently developing: > > we need to be able to update the bids for millions of keywords as fast as > possible ( order of minutes response time (!) ). > > We are currently submitting batches of 10k requests and wait for the > answer. > However this strategy is suboptimal as after each batch we wait for the > response. > > I would rather like to submit more than one batch in parallel. > > The recently introduced "bulk mutate service" seems the right candidate, > however it is surprisingly almost as slow as submitting each batch after > another, indeed retrieving the job id seems to take more time than > expected. > > One other possibility would be to build one on task queue (for example > based on celery) however, before spending such a large effort I would like > to open a discussion for suggestions and advice. > > - What is the suggested strategy for this application? > - Do you have some study case of somebody which faces a similar challenge? > - Where can I find the rate limits for keywords operations? (in other > words how fast can we get at best?) > > > Thanks! > > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
