Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Duplicate
Priority: Minor - P4
Fix Version/s: None
Affects Version/s: None
Component/s: Aggregation Framework
Labels:
None

Assigned Teams:

Query
Confidence Status:
None
Work Order:
0

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

When performing a pipeline doing a sample then project I noticed it was much slower than doing a project then sample. Could this be optimized? In a similar fashion as to: https://docs.mongodb.com/manual/core/aggregation-pipeline-optimization

For example with the MovieLens dataset ~1million documents:

Pipeline: $sample + $project _id: 76120 ms
Pipeline: $project _id + $sample: 1124 ms

duplicates

SERVER-21887 $sample takes disproportionately long time on newly created collection

Closed

SERVER-23661 $sample takes disproportionately long time on newly created collection

Closed

is related to

SPARK-64 Sampling then projecting in the MongoSamplePartitioner is slow

Closed

Assignee:: Backlog - Query Team (Inactive)

Reporter:: Ross Lawley

Participants:: Backlog - Query Team, Ross Lawley

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Created:: Jun 22 2016 10:51:29 AM UTC

Updated:: Dec 06 2022 04:23:24 AM UTC

Resolved:: Jun 22 2016 01:23:04 PM UTC