[SERVER-74370] 100MB stage memory limit for $graphLookup stage limits usability Created: 08/May/17  Updated: 27/Dec/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Muthu Chinnasamy (Inactive) Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 3
Labels: graph, query-product-scope-1, query-product-urgency-3, query-product-value-2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-23980 $graphLookup should spill to disk if ... Backlog
related to SERVER-84427 Add a query knob to configure $graphL... Backlog
Assigned Teams:
Query Execution
Participants:

 Description   

Competing with ArangoDB in an opportunity. We have a 100MB $graphLookup stage memory limit and given the large dataset at this customer it would be difficult to achieve results for them even after $match stages earlier in the pipeline.

(https://docs.mongodb.com/manual/reference/limits/#Aggregation-Pipeline-Operation)


Generated at Thu Feb 08 06:27:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.