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

Oplog performance on primary does not scale

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Operating System:
      ALL

      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

              Assignee:
              backlog-server-tuning Backlog - Tuning Team
              Reporter:
              martin.bligh Martin Bligh
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: