[SERVER-33741] Enhance capped collection deletion of small number of items in WiredTiger Created: 08/Mar/18  Updated: 29/Oct/23  Resolved: 30/May/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.0.0-rc1

Type: Improvement Priority: Major - P3
Reporter: Alexander Gorrod Assignee: Donald Anderson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-32424 Use WiredTiger cursor caching Closed
Related
related to SERVER-34559 Explore options for capped collection... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Storage Non-NYC 2018-04-23, Storage Non-NYC 2018-05-21, Storage Non-NYC 2018-06-04
Participants:

 Description   

The capped collection implementation in WiredTiger starts doing a cursor truncate once collections reach the configured maximum size. That's efficient if we are removing ranges of data, but not if only removing a few data items.

We should review the implementation to see if we can improve the performance of capped collections with WiredTiger.

Some work was done on this in SERVER-32424.



 Comments   
Comment by Githook User [ 30/May/18 ]

Author:

{'username': 'ddanderson', 'name': 'Don Anderson', 'email': 'dda@mongodb.com'}

Message: SERVER-33741 Faster capped collection deletion of small number of items in WiredTiger
Branch: master
https://github.com/mongodb/mongo/commit/98f9ed84fc1f24d74263c54f35c82f53b5e83a2b

Comment by Donald Anderson [ 06/May/18 ]

ian.whalen, alexander.gorrod, Sorry, I'm not going to be getting this into the latest sprint.

Comment by Donald Anderson [ 05/May/18 ]

pasette: the scope of this ticket got narrowed to address the case of truncating a small number items, which could be directly removed instead.  I've changed the title accordingly.

Comment by Daniel Pasette (Inactive) [ 04/May/18 ]

Was this code already committed here?  Should this be resolved?

Comment by Ian Whalen (Inactive) [ 23/Apr/18 ]

donald.anderson: Alex and I are doing sprint planning and putting this in the sprint with the assumption this will be pushed to master by May 7th. Can you give a shout if you think that's unlikely to happen?

Comment by Alexander Gorrod [ 19/Apr/18 ]

The optimization being addressed here will be to avoid setting up for a truncate if only a small number of entries are going to be removed.

Comment by Donald Anderson [ 10/Apr/18 ]

Code review url: https://mongodbcr.appspot.com/198200002

Generated at Thu Feb 08 04:34:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.