-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Aggregation Framework
-
Query Optimization
-
ALL
-
Query 2017-08-21, Query 2017-09-11
-
(copied to CRM)
In cases where we can use the optimized sampling from a random cursor, the DocumentSourceCursor will still use the default batch size. This can significantly slow down small sample sizes.
Unfortunately, we cannot just pass down a limit to the DocumentSourceCursor, since the random cursor may give back duplicate documents, in which case we'd need to ask for more.
- duplicates
-
SERVER-79862 Exponential batch size growth in DocumentSourceCursor
- Closed
- is duplicated by
-
SERVER-23661 $sample takes disproportionately long time on newly created collection
- Closed
-
SERVER-30342 Slow performance of $project in aggregation pipeline in 3.4.6
- Closed