-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
None
-
None
-
None
-
None
-
None
-
None
-
None
For each query, we should record some basic information: the winning plan chosen, the optimal plan, if there are plan flips, the variance in latency, and how random sampling (vs chunked sampling) impacts the latency and plan chosen.
At the end of this investigation, we should have an idea of whether or not we are choosing near-optimal join orders (and algorithms) for all of these queries and, if not, where we should focus our improvements.
The random sampling investigation is to understand SERVER-118980. We should also understand the interaction with SERVER-117085. Perhaps after that ticket, we don’t need random sampling for TPC-H – for now – since we are able to make use of unique fields. See also SERVER-119639.
- is related to
-
SERVER-118980 Use random sampling for join optimization by default
-
- Closed
-
-
SERVER-119639 Enable use of index uniqueness metadata and revisit join performance testing configs
-
- Open
-
-
SERVER-117085 Avoid NDV computation if we have a unique index on the joining fields
-
- Closed
-
1.
|
Q3 investigation | SERVER-119849 |
|
Closed | Hana Pearlman | |
2.
|
Q5 investigation | SERVER-119850 |
|
Closed | Hana Pearlman | |
3.
|
Q7 investigation | SERVER-119851 |
|
Closed | Ben Shteinfeld | |
4.
|
Q8 investigation | SERVER-119852 |
|
Closed | Hana Pearlman | |
5.
|
Q9 investigation | SERVER-119853 |
|
Closed | Ben Shteinfeld | |
6.
|
Q10 investigation | SERVER-119854 |
|
Closed | Alya Berciu |