-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
-
None
-
None
-
None
-
None
-
None
-
None
-
None
An idea to fix the problem with LIMIT is to calculate what percentage of the cardinality of the child node the limit value is, and set the LIMIT's cost to be that percentage of the child's cost.
As max.verbinnen@mongodb.com pointed out: If we do this, then costs won't be purely cumulative anymore though as the cost of LIMIT could be smaller than its child