Reference framework for building data workflows provided by Google. Accelerates authentication, logging, scheduling, and deployment of solutions using GCP. To borrow a tagline.. "The framework for professionals with deadlines."
Apache License 2.0
165
stars
49
forks
source link
Performance Tuning: DV360 Bulk Editor Recipe Run Times Lagging #53
For users who filtered on a non-TEST DV360 advertiser, and only 1 campaign under selected advertiser, when they went to Load Insertion Orders & Line Items, it was taking 60+ minutes to barely load the first tab of Insertion Orders, let alone all the other tabs. However, users who filtered on the TEST advertiser had theirs complete within normal running time.
The following will show you that it was taking 19+ minutes to read the Advertisers tab in my sheet.
Not sure if we can pin point what might have been the cause. Since everyone filtered on an Advertiser AND a Campaign, I can’t imagine the Campaign under non-TEST advertisers were significantly larger, if anything the opposite, because our TEST campaigns have a ton of IOs / Line Items loaded under them from QA.
UPDATE: User confirmed the following day that recipe eventually Errored and shared the following log:
For users who filtered on a non-TEST DV360 advertiser, and only 1 campaign under selected advertiser, when they went to Load Insertion Orders & Line Items, it was taking 60+ minutes to barely load the first tab of Insertion Orders, let alone all the other tabs. However, users who filtered on the TEST advertiser had theirs complete within normal running time.
The following will show you that it was taking 19+ minutes to read the Advertisers tab in my sheet.
Not sure if we can pin point what might have been the cause. Since everyone filtered on an Advertiser AND a Campaign, I can’t imagine the Campaign under non-TEST advertisers were significantly larger, if anything the opposite, because our TEST campaigns have a ton of IOs / Line Items loaded under them from QA.
UPDATE: User confirmed the following day that recipe eventually Errored and shared the following log: