BatchJob performance issues

[Thorsten Merz]

Hey there,

it seems that starting today we are experiencing performance issues with the batch job service (API v201710).

Usually our batchjobs take only seconds to finish up to 1-2 minutes. Since today our batch jobs run within 10, 20, 30 or even 60 minutes with similar amount of operations and operation types.

Are there any specific issues currently ongoing with the batch  job queue / service / API?

BatchID  example: 743564948

Some help on how to resolve these issues would be appreciated.

Regards

Thorsten

(Sorry if this is a double post - seems something went wrong with my first post)

[Dhanya Sundararaju (AdWords API Team)]

Hi Thorsten,

We are looking into this issue. At this point, there is no ETA but I will keep you posted on the updates. 

Regards,
Dhanya, AdWords API Team

[Thorsten Merz]

Hi Dhanya,

thank you for looking into it. The performance of the batch job processing has increased since yesterday, but it still feels "slow" compared to the speed we were getting some days ago.

In addition to this, I am noticing that many batchjobs seem to be executed and marked as successful, while the Status of the batch job still stays on ACTIVE instead of switching to DONE.

Example:

Job in progress:

2018-05-24T10:05:27+02:00 CRIT (2): B: 744565774 - Total #:1 - Executed #: 0 - Success #: 0 - Progress %: 0 - Status: ACTIVE - Checking batch job!

Job at 100%:

2018-05-24T10:05:38+02:00 CRIT (2): B: 744565774 - Total #:1 - Executed #: 1 - Success #: 1 - Progress %: 100 - Status: ACTIVE - Checking batch job!

...

Job still at 100% after around 4-5 minutes:

2018-05-24T10:11:18+02:00 CRIT (2): B: 744565774 - Total #:1 - Executed #: 1 - Success #: 1 - Progress %: 100 - Status: ACTIVE - Checking batch job!

...

Job finished after around 8 minutes:

2018-05-24T10:13:12+02:00 CRIT (2): B: 744565774 - Total #:1 - Executed #: 1 - Success #: 1 - Progress %: 100 - Status: DONE - Completed batch job!

--

The example batch job only has one single Operation to be executed. In this case it would most likely have been a better idea to just execute the single mutate operation directly, yes. Due to the variable size of operations ranging from 1 - 1000+ the same logic is applied in any case currently.

Regardless of the amount of operations I would still expect the batch job to be executed the same way though.

[Dhanya Sundararaju (AdWords API Team)]

Hi Thorsten,

Thank you for sharing the details. At this point, there is no update on the issue but we are actively working on it. I will keep you posted.

[Ершов Александр]

Hello, Dhanya!

We are experiencing the same issue.

I can provide BatchJob IDs / clientCustomerIds if that helps!

Let me know if that helps!

Best wishes,

Ershov Alexander

[Dhanya Sundararaju (AdWords API Team)]

Hi Ershov,

Thank you for reaching out. We are aware of this issue and currently actively working on it. At this point I have no updates. I will keep you post on this thread.

[Milind Sankeshware (AdWords API Team)]

Hi,

I am Dhanya's colleague and will be following up on this thread as she is unavailable today. We have an update from our team, there was an issue which is currently resolved. Could you please try your batch job request again and let me know if you are facing issues?

Thanks,
Milind, AdWords API Team.

[Ершов Александр]

Hello, Milind Sankeshware!

We're pushing every day. Since that we haven't experiencing it very much.

I will reach to you if we see this issue coming up again.

Thank you very much for you work!