-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage, WiredTiger
-
None
-
Storage Execution
At the moment capped collections generally end up removing a small number of documents at a time when they reach the capped size.
We had success with optmizing how the oplog maintains it's size, by removing a larger volume of entries at a time. We could make capped collections much faster by making a similar change, and removing a proportion of the documents to maintain the collection size.
There are references in the code to count based capped collections requiring, but our documentation doesn't mention that requirement, in fact it says that the size restriction means we don't guarantee that the count will be accurately maintained.
- is related to
-
-
- Closed
-
- related to
-
SERVER-64186 Evaluate doing batched capped deletes in CollectionImpl::_cappedDeleteAsNeeded
-
- Open
-
-
-
- Blocked
-