[SERVER-75294] Investigate slowness of sharded $lookup Created: 26/Mar/23 Updated: 07/Aug/23 Resolved: 07/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Katya Kamenieva | Assignee: | Hana Pearlman |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Sprint: | QO 2023-05-15, QO 2023-05-29, QO 2023-06-12, QO 2023-06-26, QO 2023-07-10, QO 2023-07-24, QO 2023-08-07, QO 2023-08-21 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
When both collections are sharded, lookup queries are ~2x slower than for non-sharded collections. |
| Comments |
| Comment by Hana Pearlman [ 04/Aug/23 ] |
|
Belatedly closing this ticket now, because we don't intend to do any more work on it. The improvement to skip the network for a $lookup subpipeline when a shard is targeting only itself ( |