Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-34559

Explore options for capped collection performance improvements

    XMLWordPrintable

Details

    • Improvement
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Storage, WiredTiger
    • None

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              alexander.gorrod@mongodb.com Alexander Gorrod
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated: