Investigate and fix slow bulkWrite response cursor population on mongod

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • Fully Compatible
    • Repl 2023-10-30
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      According to the flame graph, about 4% of the bulkWrite operation's time is spent in populating the cursor response on mongod (when a bulkWrite with 1000 insert operations is run). When I eliminated this method (by returning an empty cursor response instead here) I saw the corresponding improvement.

      Consider ways to optimize this method. And if possible, consider omitting success responses from the response and use a counter n instead, as the existing insert codepath does.

      See SERVER-76662 for flame graphs.

            Assignee:
            Sean Zimmerman
            Reporter:
            Vishnu Kaushik
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: