Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Querying
Labels:
None

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
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

When both collections are sharded, lookup queries are ~2x slower than for non-sharded collections.
Let's understand what is the cause of this impact on performance.

duplicates

SERVER-77427 Avoid going through the network when a shard is targeting only itself for a $lookup subpipeline

Closed

is related to

SERVER-77427 Avoid going through the network when a shard is targeting only itself for a $lookup subpipeline

Closed

related to

SERVER-58727 Perform local operation when AsyncRequestsSender only targets local shard

Closed

SERVER-75732 Cache $lookup single solution inner queries when sharded

Closed

Assignee:: Hana Pearlman
Reporter:: Katya Kamenieva
Participants:: Hana Pearlman, Katya Kamenieva
Votes:: 0 Vote for this issue
Watchers:: 14 Start watching this issue

Created:: Mar 26 2023 08:21:00 PM UTC
Updated:: Aug 07 2023 12:38:59 PM UTC
Resolved:: Aug 07 2023 12:38:59 PM UTC
Confidence Status Last Update:: 24/Apr/23 2:36 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates