Investigate why throughput of updateMany did not improve

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      To measure the impact of SERVER-60176, we create genny benchmark UpdateLargeDocuments. We expected improvement in both updateOne and updateMany stages of this workload. Unfortunately, only updateOne has seen improved throughput (see BF-23705). We need to investigate why throughput of updateMany stayed the same.

            Assignee:
            [DO NOT USE] Backlog - Query Execution
            Reporter:
            Nikita Lapkov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: