[SERVER-62807] Ensure refresh performance is not affected by sharded catalog index refresh Created: 20/Jan/22  Updated: 07/Feb/23  Resolved: 06/Feb/23

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

Type: Task Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Marcos José Grillo Ramirez
Resolution: Won't Do Votes: 0
Labels: PM-2583-Milestone-2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-72323 Improve the first refresh of a stale ... Closed
Duplicate
Assigned Teams:
Sharding EMEA
Sprint: Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06
Participants:

 Description   

The normal refresh scenario should not be affected by changes for PM-1965, a regular incremental refresh due to stale data placement data should not incur in extra latency due to the presence of indexes in the sharded index catalog. The outcome of this ticket should be a measurement of the behavior of refreshes before and after the catalog cache changes, in order to ensure we're not penalizing regular collections operation due to the new refresh scheme.



 Comments   
Comment by Marcos José Grillo Ramirez [ 06/Feb/23 ]

The current performance evaluations executed by the workloads repo are enough to determine the only important performance hit is tracked by SERVER-72323, so closing this ticket as won't do because there is no more work to do.

Comment by Marcos José Grillo Ramirez [ 17/Jan/23 ]

This ticket can only continue after SERVER-72323 is committed.

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