Keep track of the next record to delete in capped collections

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.0-rc0
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Execution Team 2021-04-05
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Gregory Wlodarek
              Reporter:
              Gregory Wlodarek
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: