-
Type:
Task
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
We calibrated first version of Cost Model with some simplifications in mind, one of them was that the cost of an ABT node depends on the number of incoming (processed) documents. As we highlighted in the design doc this assumption not correct for all ABT nodes.
The following nodes can be relatively easy to improve:
- Filter node - we need to take into account number of predicates in its expression
- Evaluation node in case of simple projections (show/hide fields) by taking into account number of the fields.
- is duplicated by
-
SERVER-79635 [CQF] Consider the number of projections produced by a PhysicalScan when determining its cost
-
- Closed
-
- related to
-
SERVER-79633 [CQF] Consider the expression child of an EvaluationNode when determining its cost
-
- Closed
-