[SERVER-75732] Cache $lookup single solution inner queries when sharded Created: 05/Apr/23  Updated: 22/Jan/24  Resolved: 22/Jan/24

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

Type: Improvement Priority: Major - P3
Reporter: Matt Boros Assignee: Hana Pearlman
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-76684 Cached plans from inner $lookup singl... Open
Related
is related to SERVER-75294 Investigate slowness of sharded $lookup Closed
Assigned Teams:
Query Optimization
Sprint: QO 2024-02-05
Participants:

 Description   

In SERVER-75506, caching single solution queries on the inner side of a non-sharded $lookup lead to a positive performance impact. This could have a positive impact on sharded lookup as well, but some performance investigation should be done first.

For this ticket we should implement this change for sharded $lookup, analyze the perf impact, and make a decision about whether to commit it or not.



 Comments   
Comment by Matt Boros [ 18/Apr/23 ]

I believe we were planning on wrapping up PM-3210 last week (correct me if I'm wrong Kyle). Also the related ticket SERVER-75294 doesn't seem specific to 7.0, my understanding is it's a more general comparison of unsharded lookup to sharded lookup. Since it's not 7.0 specific I don't think it fits into PM-3210.

Comment by Ana Meza [ 18/Apr/23 ]

matt.boros@mongodb.com kyle.suarez@mongodb.com can this ticket be done as part of PM-3210?

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