SQL-3178: Disable Q12 in TPCH monthly benchmark#134
Conversation
Q12 times out due to the OR de-optimization regression (SQL-3118), consuming the entire 24h task budget and blocking all subsequent queries from running. Replace with NoopPhase to keep phase numbering intact.
|
Did you create a patch that shows the task now completes for all other queries? Can you share the link if so -- I'm curious to see the numbers lately since the last 3 months are red and the next one won't run automatically until end of month. |
|
@mattChiaravalloti I kicked it off last night and its still running haha: https://spruce.corp.mongodb.com/task/mongosql_tpch_monthly_tpch_0.1_normalized_atlas_sql_patch_823c5e023c34a02827d1afb9b753efcac084d65b_69d32036ef76be0008c75894_26_04_06_02_53_53/logs?execution=0 there are other slow queries that are potentially non-blocking (ie take 1-2 hours) so wanted to see if just removing 12 will get the benchmark to pass. will be keeping my eye on this one tho |
Cool yea so let's hold off on merging this until that finishes just to be totally sure |
Q19 also times out due to the OR de-optimization regression (SQL-3118), consuming the remaining 24h task budget after Q12 was disabled.
3 participants
Q12 times out due to the OR de-optimization regression (SQL-3118), consuming the entire 24h task budget and blocking all subsequent queries from running. Replace with NoopPhase to keep phase numbering intact.