Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: unspecified
-
Fix Version/s: None
-
Component/s: Bid Management Tool
-
Labels:None
-
Environment:
Operating System: Linux
Platform: PC
-
Bugzilla Id:3303
Description
In Spark Black Singles, there were 3 time based bidding jobs scheduled like so:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1. row ***************************
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
id: 205
name: Lower Bids 15% - Black Pictures
accountID: 435
startDOW: sunday
startTime: 00:00:00
endDOW: sunday
endTime: 23:00:00
pause: false
positionDelta: 0.000
positionDeltaType: abs
bidDelta: 0
bidDeltaType: abs
recurrence: sunday,tuesday
adMaxMetricDelta: 15
adMaxMetricDeltaType: pct
adMaxBidMinDelta: -15
adMaxBidMinDeltaType: pct
adMaxBidCapDelta: -15
adMaxBidCapDeltaType: pct
lastBidTime: 2009-10-20 21:10:35
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 2. row ***************************
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
id: 215
name: Boost 20% - Generic Singles
accountID: 435
startDOW: sunday
startTime: 00:00:00
endDOW: sunday
endTime: 23:00:00
pause: false
positionDelta: 0.000
positionDeltaType: abs
bidDelta: 0
bidDeltaType: abs
recurrence: sunday,tuesday,wednesday,friday
adMaxMetricDelta: -20
adMaxMetricDeltaType: pct
adMaxBidMinDelta: 20
adMaxBidMinDeltaType: pct
adMaxBidCapDelta: 20
adMaxBidCapDeltaType: pct
lastBidTime: 2009-10-21 23:12:38
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 3. row ***************************
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
id: 225
name: Boost 30% - Black Chat
accountID: 435
startDOW: wednesday
startTime: 00:00:00
endDOW: wednesday
endTime: 23:00:00
pause: false
positionDelta: 0.000
positionDeltaType: abs
bidDelta: 0
bidDeltaType: abs
recurrence: wednesday,friday,saturday
adMaxMetricDelta: -30
adMaxMetricDeltaType: pct
adMaxBidMinDelta: 30
adMaxBidMinDeltaType: pct
adMaxBidCapDelta: 30
adMaxBidCapDeltaType: pct
lastBidTime: 2009-10-21 23:12:38
3 rows in set (0.03 sec)
There were a couple of problems. We ended up with more time based bidding jobs
running than were scheduled:
OK
End Time Node CPU Time Wall Time Memory Std. Out Std. Error
2009-10-22 02:02:36 tyanb2881-dc1bos0003 00:00:27 00:00:20 119464kb
2009-10-21 23:12:46 pngal650-dc1bos0001 00:00:17 00:00:33 213620kb
2009-10-21 16:03:46 tyanb2881-dc1bos0002 00:00:23 00:00:30 208856kb
2009-10-21 10:03:32 tyanb2881-dc1bos0004 00:00:16 00:00:10 0kb
2009-10-21 07:03:06 tyanb2881-dc1bos0004 00:00:17 00:00:10 0kb
2009-10-21 04:03:30 tyanb2881-dc1bos0004 00:00:15 00:00:09 0kb
2009-10-21 01:01:45 tyanb2881-dc1bos0003 00:00:20 00:00:14 0kb
2009-10-20 21:10:56 tyanb2881-dc1bos0004 00:00:34 00:01:17 207252kb
And it appears that some bids may be being changed outside of the bounds of the
jobs. In this case from 5.00 to 2.00. bidHistory shows:
| 498242375 | 2009-10-21 14:18:22 | 129991195 | 5.000 | 2.000 |
NULL |
| 498289015 | 2009-10-21 16:03:31 | 129991195 | 2.000 | 2.000 |
NULL |
I wonder about the bids though - the one from 16 corresponds with a time based
bidding run. The one from 14 does not though it does not correspond to anything
in the bid history tied to an AM either.
