Hi Anash,
Thank you very much and I really appreciate your honest attempt to
understand my case and offer your opinion.
Thank you. My concerns have been resolved now :)
Kruger,
On Thursday, July 6, 2017 at 10:13:19 AM UTC-4, Anash P. Oommen (AdWords
API Team) wrote:
>
> Hi Kruger,
>
> Looks
Hi Kruger,
Looks to me like the workload that you have to process isn't high -
assuming you want to update bids for all the keywords in a single account,
you are looking at ~3*100*10 = 3000 mutate operations per account. As you
guessed, you can easily spread it over ~10 synchronous calls per
Hello,
Yes I have read both pages before writing my question.
Your answer, at best, only summarize the pages I have already read. (I even
recognize some specific phrases you nearly CP'ed from the pages)
I have provided a specific situation for the effectiveness of implementing
BatchJobService
Hi,
Making a request to the API entails a number of fixed costs, such as
round-trip network latency, serialization and deserialization processing,
and calls to backend systems. By batching multiple operations, you can
reduce the number of requests you make and the associated fixed costs.
Hello,
I am quite curious on the amplitude of increase in efficiency when using
BatchJobService as opposed to having all calls synchronously.
Given that I have less than 1,000 customer accounts and I make reasonable
amount of scheduled calls daily and some more weekly, how much would Batch
