[SERVER-57343] Investigate sharding optimizations for DocumentSourceDensify Created: 01/Jun/21  Updated: 06/Dec/22

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

Type: Task Priority: Minor - P4
Reporter: Joe Kanaan Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-57340 Add support for partitioning in Docum... Closed
Related
Assigned Teams:
Query Optimization
Sprint: QO 2021-10-18, QO 2021-11-01, QO 2021-11-15, QO 2021-11-29, QO 2021-12-13, QO 2021-12-27, QO 2022-01-10, QO 2022-01-24, QO 2022-02-07, QO 2022-02-21, QO 2022-03-07, QO 2022-03-21, QO 2022-04-04, QO 2022-04-18, QO 2022-05-02, QO 2022-05-16, QO 2022-05-30, QO 2022-06-13, QO 2022-06-27, QO 2022-07-11, QO 2022-07-25, QO 2022-08-08, QO 2022-08-22, QO 2022-09-05
Participants:

 Description   

See the sharding section of the design doc. The goal of this ticket is to determine whether there are any pitfalls to pushing work to the shards, in addition to determining whether doing so helps performance in sparse collections. While not strictly dependant on the performance test tickets, it would be useful to have the performance tests runnable for the second part of this investigation.



 Comments   
Comment by Ana Meza [ 05/Sep/22 ]

Removing Sprint since this ticket is in the Backlog and assigned to the QE BacklogĀ 

Generated at Thu Feb 08 05:41:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.