Oplog performance on primary: efficiency of uncommitedRecordIds

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • 3.1.9
    • Affects Version/s: None
    • Component/s: Concurrency
    • None
    • Fully Compatible
    • QuInt A (10/12/15)
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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:
            Gregory McKeon (Inactive)
            Reporter:
            Martin Bligh (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: