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.
- related to
-
SERVER-82863 Add support for the new capped collection option 'allowConcurrentWrites'.
- Closed