"ADD" keywords operations : Concurrent vs. sequential

[GDZ]

Hello!

Not really a question but an observation.

Situation: 5 AdGroups, ~500 keywords each. Keywords ADD operations are "batched" into one mutate job for each AdGroup. So naturally 5 mutate jobs total ready for execution.

Scenario 1. Mutate jobs are executed one after another, i.e. next job starts only after the previous one was finished.

Scenario 2. Mutate jobs are executed in parallel, 5 threads are running at the same time, each modifying its own AdGroup to avoid CONCURRENT_MODIFICATION error.

Naturally, we expected Scenario 2 to be much faster than Scenario 1, reality is its only ~6% faster. Now trying to figure out how to speed this up a bit :)

Thank you,

GDZ

[Anash P. Oommen (AdWords API Team)]

Hi GDZ,

Are you sure your machine is not blocking on outgoing connections? .NET, for instance, limits the number of simultaneous Web connections to 2.

Cheers,
Anash P. Oommen,

AdWords API Advisor.

[GDZ]

Absolutely no blocking. We're for example running 20 threads concurrently to get accounts report data without any problems... Blazing fast.

[GDZ]

Still unclear how to fix that...

On Wednesday, October 29, 2014 5:32:42 PM UTC-4, GDZ wrote:

[Anash P. Oommen (AdWords API Team)]

Hi,

You are using AdGroupCriterionService, right? What kind of responseTimes are you seeing in the SOAP response header of the API calls?

Cheers,

Anash

[GDZ]

Don't have access to log files right now, will check later. 

But for now it appears that using MutateJobService is a way to go for us at the moment so we switched to MJS.

Thank you,

GDZ