[SERVER-18733] Streamline set cache optimization for set operations Created: 29/May/15  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: Antoine Hom Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 1
Labels: asya, optimization
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-18734 The match $in operator is using a Val... Closed
Assigned Teams:
Query Optimization
Participants:

 Description   

In the $project stage of the aggregation framework one set operation ($setIsSubset) has a performance optimization (caching a constant set) which provides tremendous benefits if the set used is big enough.

I think it would be nice to streamline this optimization to all set operations as it is easy to implement and they could benefit from it.

Here is the link to the code implementing this optimization: https://github.com/mongodb/mongo/blob/master/src/mongo/db/pipeline/expression.cpp#L2354



 Comments   
Comment by Antoine Hom [ 29/May/15 ]

SERVER-18732 Explains the background of why we tried to use big sets in set operations.

Generated at Thu Feb 08 03:48:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.