[SERVER-65528] Use range bounded cursors for restoring index cursors after yielding Created: 13/Apr/22  Updated: 29/Oct/23  Resolved: 14/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Deepti Hasija Assignee: Shin Yee Tan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-56274 TTL deletes are much slower on descen... Closed
is depended on by SERVER-57221 Inconsistent delete performance on co... Closed
Problem/Incident
Related
is related to SERVER-69659 Test performance of restoring index c... Open
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-08-08, Execution Team 2022-08-22, Execution Team 2022-09-05, Execution Team 2022-09-19
Participants:
Linked BF Score: 105

 Description   

TTL indexes reposition the cursor often to continue deleting the obsolete records. The repositioning uses a search_near which is biased to walk in one direction looking for the records than the other. This could cause a performance issue if the cursor has to walk through a lot of deleted records. The bounded cursor offers a means to limit the range the search_near has to walk, potentially improving the performance.



 Comments   
Comment by Githook User [ 14/Sep/22 ]

Author:

{'name': 'Shin Yee Tan', 'email': 'shinyee.tan@mongodb.com', 'username': 'shinyeet'}

Message: SERVER-65528 Set bounds when restoring index cursors
Branch: master
https://github.com/mongodb/mongo/commit/790dde10c5f653c65b394cf397e96d099e2f5d03

Generated at Thu Feb 08 06:02:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.