Hi Supraja, I'd say that 60 seconds is a good retry interval. The throughput of MJS depends a lot on our server loads too, so wait time is something I'd ideally remove from my code. If that can't be accomplished, then aim a higher wait time (say, 10 minutes), 5 minutes sounds low for updating 300000 keywords.
Also, make sure you try to group the jobs with keywords within the same ad group (even if that means more jobs), since that will give a better throughput. Cheers, Anash P. Oommen, AdWords API Advisor. On Wednesday, 14 March 2012 03:09:46 UTC+5:30, dsr wrote: > > Hi, > > We have been using mutateJobService to update keyword bids. (using > AdGroupCriterionOperation SET). > We have to process around 300000 keywords so been using 10000 operations > per job. Get result for each job , do some internal processing and then > proceed with next job(i.e next10000 keywords). We were using retry interval > as 60 secs and wait time as 5 minutes. We were able to get results within 1 > or 2 minutes when we had fewer keywords to update(i.e. between 10000 to > 100000) but as the number of operations increased the response time > increased and could not get result within the 5 minute interval. So could > you suggest the optimal wait time and retry interval to get result for each > job. > > I appreciate you time and help. > > Thanks > Supraja > -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
