Details
-
Type:
Improvement
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Google
-
Labels:None
Description
It's probably worth looking into this, because the difference checking should be a fast operation, but once we start using the replicated temp table, and checking bid type and bid amount changes, it slows down. I'm fairly certain we can take some of the logic in the code when it iterates through the resultset and stick it into SQL Bid detection is taking over an hour for IdentityGuard, and this is consistent with other accounts as well.
2010-05-27 12:10:12.196 (3) [P1T1]: – Account-level operations complete for seuser ((2025) "Identity Guard") and seAccount(687)
2010-05-27 12:10:16.147 (3) [P1T1]: Replicating 44614 rows...
2010-05-27 12:59:37.784 (3) [P1T1]: Keyword-level bidType changes: 0
2010-05-27 12:59:37.785 (3) [P1T1]: Keyword-level bidAmount changes: 0
2010-05-27 12:59:37.785 (3) [P1T1]: COMPLETED KEYWORD-LEVEL BID DETECTION FOR: seUser (2025) and seAccount(687)
2010-05-27 13:28:50.065 (3) [P1T1]: Adgroup-level bidType changes: 0
2010-05-27 13:28:50.065 (3) [P1T1]: Adgroup-level bidAmount changes: 0
2010-05-27 13:28:50.065 (3) [P1T1]: COMPLETED ADGROUP-LEVEL BID DETECTION FOR: seUser (2025) and seAccount(687)
