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

Oplog performance on primary does not scale

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • ALL

      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

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

              Created:
              Updated:
              Resolved: