[SERVER-55512] Keep track of the next record to delete in capped collections Created: 25/Mar/21  Updated: 06/Feb/24  Resolved: 25/Mar/21

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

Type: Improvement Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-82863 Add support for the new capped collec... In Progress
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-04-05
Participants:
Linked BF Score: 0

 Description   

We should keep track of the next record up for deletion in capped collections as an optimization. Using a cursor and advancing it to the first element will be slow for capped collections on WiredTiger. This is because WiredTiger will have to traverse over tombstoned records at the beginning of the table. Knowing the next record to delete and seeking to it alleviates this problem.



 Comments   
Comment by Githook User [ 25/Mar/21 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-55512 Enable additional tests on ephemeralForTest
Branch: master
https://github.com/mongodb/mongo/commit/d24fbc3f38e3c0d7b983be0312dfd56dc2bc082b

Comment by Githook User [ 25/Mar/21 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-55512 Keep track of the next record to delete in capped collections
Branch: master
https://github.com/mongodb/mongo/commit/160b14eb711a9242698ec02b9c45250cfa520543

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