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

Oplog performance on primary: efficiency of uncommitedRecordIds

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.1.9
    • Concurrency
    • None
    • Fully Compatible
    • QuInt A (10/12/15)

    Description

      32 threads insert, 24 CPU box.
      standalone: 1.15M insert/s
      with oplog: 186K insert/s

      Believed to be single threading in logOp from OplogHack mutex.
      Contention from delete holding mutex whilst walking DLL is linear with list size.
      Proposed fix of O(1) delete by retaining pointer handle to reference back

      Attachments

        Issue Links

          Activity

            People

              greg.mckeon@mongodb.com Gregory McKeon (Inactive)
              martin.bligh Martin Bligh
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: