[SERVER-57668] Cache chunk bounds as an array in resharding collection cloning pipeline - MongoDB Jira

XML

Word

Printable

Details

Type: Improvement
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 5.0.0-rc2, 5.1.0-rc0
Component/s: Sharding
Labels:

Backwards Compatibility:
Fully Compatible
Backport Requested:

v5.0
Sprint:
Sharding 2021-06-28
Story Points:
1

Description

DocumentSourceSequentialDocumentCache::doOptimizeAt() caches on a per-stage basis of the $lookup pipeline. Restructuring the aggregation pipeline so the $objectToArray values are done as a separate stage from the $match that references the $$sk variable would mean their results can be cached too.

The changes made in this ticket will be obsoleted by ~~SERVER-57667~~ but will reduce the per-document processing overhead by a constant factor.

Attachments

Issue Links

is related to

SERVER-57579 DocumentSourceSequentialCache doesn't clone, ruining non-correlated $lookup pipeline caching in sharded deployments

Closed

SERVER-57667 Improve processing speed for resharding's collection cloning pipeline

Closed

related to

SERVER-57705 DocumentSourceSequentialCache can wind up in a suboptimal location due to optimizations

Backlog

SERVER-57483 Results from $lookup stage are not cached for a resharding operation's sub-pipeline

Closed

Activity

People

Assignee:: Max Hirschhorn

Reporter:: Max Hirschhorn

Participants:: Githook User, Max Hirschhorn, Vivian Ge

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: Jun 12 2021 06:38:52 PM UTC

Updated:: Oct 06 2021 07:29:58 PM UTC

Resolved:: Jun 16 2021 03:21:37 AM UTC