-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Querying
-
None
-
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
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