-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We currently don't take memory consumption into account for the SORT node. We've noticed however that we can severely underestimate the cost of a SORT stage, because it might spill data to disk in case of large inputs.
One idea might be to look at the threshold for when we spill to disk. Then, you could estimate the needed spills by looking at average document size & input cardinality.
- is related to
-
SERVER-113990 Take SORT spilling into account for $sort + $limit
-
- Needs Scheduling
-
- related to
-
SERVER-107790 Design workload for SORT node
-
- Closed
-
-
SERVER-104684 Take into account memory cost for blocking plans
-
- Needs Scheduling
-
-
SERVER-100603 Consider average document and key size in cost model
-
- Needs Scheduling
-