[SERVER-36719] Investigate optimizations for aggregate with single $out stage Created: 17/Aug/18 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query Optimization
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
With removal of several commands that copied one collection to another aggregation with single $out stage becomes the logical replacement for this functionality. This ticket is to track performance improvements for this exact pipeline: db.foo.aggregate([{$out:"xxx"}]). |
| Comments |
| Comment by Asya Kamsky [ 13/Jun/19 ] |
|
Would like to consider whether it's feasible to optimize this pipeline. If so would this be a storage or query project? |
| Comment by Kyle Suarez [ 17/Aug/18 ] |
|
What is the proposed optimization? Some sort of storage-level feature that would bypass the aggregation framework (and the BSON-Document-BSON conversions) altogether, and do a direct copy of data? |