BatchJob v201603 very slow

[Stefano Fontana]

Hello,

Same as in https://groups.google.com/forum/#!newtopic/adwords-api/adwords-api/1zv1-t0YZDY my batch job are sometimes extremely slow.

For example https://batch-job-download-prod-ebe9b43.storage.googleapis.com/109310708/38018871.results.xml?GoogleAccessId=926043054183-rbu1gkdus...@developer.gserviceaccount.com&Expires=1462438137&Signature=O9pHimDZB%2Bn0HIGWG8mfz19UXiJXsIXgekPTsxVfO6wZRY0q1uH2gYpj65wEccvCOQPM4QvGQYXYM99UjqRfXCfYg2UhXcA9YZQ5oPgZQfsONTPWhpJZzQWiLtn58ZIU%2FKwKDCSYGGnO8iE6ws9wdePN165myYvvfklLM%2Fk5Tsj828Nm4rE%2F%2FnqjcRY0kVkxkOOBu9xjflFK%2BpjQEPxAp2bRbEFGIpFIt%2FYWS7mIgz%2BKIhv8AaDyDz8GJRGpvuVMGON2vUo8EblkAyHf8GlAT6Q2RsO%2BvialbbXS2170Q9%2FsFy3wgS6MVTFfWDVKgvas9GE7CtCfQ8l8l%2FJHIEH53Q%3D%3D

executed 2 operations and took more than 3 minutes to complete.

To me it also seems that this is happening more frequently compared to a couple of weeks ago.

The long waiting periods seem to be independent from the type of operations I am sending.

 

Is there anything I can do to avoid this behaviour?
Will the service be stabilised in the future?

Cheers,

   Stefano-

[Yin Niu]

Hi Stefano, 

Could please send your SOAP logs to us by Reply privately to author?

Thanks,

Yin, AdWords API Team. 

[Stefano Fontana]

I've sent the logs privately, let me know what I can do.

[Umesh Dengale]

Hi Stefano,

Thanks for attaching the BatchJobService log. I have gone through few errors in log file. There is a ClientTermsError. It describes that you have not agreed to the latest AdWords Terms & Conditions. You could login to your manager account (MCC) and click on a gear icon on top right corner. Please select Account settings --> AdWords API Center and you could see the terms and conditions.

Regards,

Umesh, AdWords API Team.

[Stefano Fontana]

Hello Umesh, 

The ClientTermsError appears in the log because suds it's also printing the wsdl.

I don't think that's the culprit for the extremely slow jobs. I double check my account just to be sure.

Moreover these jobs do terminate sometimes.

Looking forward to solving this problem asap.

S-

[Stefano Fontana]

Another detail:

The jobs do complete ..sometimes even 1 hour later, which is not very useful.

As a temporary fix I'm cancelling the jobs that seem to take too long and re-submit them.

Once they are re-submitted they run within a few seconds.

[Michael Cloonan (AdWords API Team)]

Hello,

I grabbed one of the batch jobs out of your log and it only took 28 minutes to complete, which seems fairly reasonable to me. What threshold would you consider that it is taking too long? The advantage of batch jobs is not with the speed of execution but the fact that you can send many operations at once and the API will automatically handle retrying and rate limiting logic for you. If you are sending many operations, you should expect that it may take a significant amount of time.

Regards,

Mike, AdWords API Team

[Stefano Fontana]

Hello Mike,

The logs I sent were for only 4 operations (you can grep by "Operations uploaded") so 28 minutes is a very long time IMHO.

Moreover the behaviour is not always consistent, as I mentioned earlier if I cancel the job and start a new one with the very same operations it takes only 10 seconds (90% of the times, but then I cancel and retry again). It's as if I was being served by a slow server from time to time.

I think the auto-retrying and rate-limit logic is great, but I think this issue should be investigated before v201509 is sunset.

If there's no such thing as a limping server maybe the scheduling logic could be reviewed, IMHO a job with few operations should be executed much faster than a job with thousands of operations but from what I see this is not the case oftentimes.

I am surprised that only few other people reported this issue, perhaps many are still using the older version. 

I also observed that there are days where the jobs are very slow (like today) and others where the jobs are only somewhat slow.

[Michael Cloonan (AdWords API Team)]

Hello,

Since you're contributing on the other thread (https://groups.google.com/forum/#!msg/adwords-api/J6fDOsLQkpc/OWQQXDQoMgAJ) along with some others, I would like to consolidate the conversation to that one location. We'll keep track of the issue there.

Our engineering team is investigating and I will respond there when I have more to share.

Regards,

Mike, AdWords API Team