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

Perf regression with mongodump integration tests

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.0-rc4
    • Component/s: None
    • Labels:
      None
    • Environment:
      darwin Sierra, linux Ubuntu 17.10
    • Storage Execution
    • ALL
    • Hide
      • Install Go (my test used Go 1.9.2)
      • Clone the mongo-tools repo
      • cd into the directory and check out commit 9c973cbf
      • run `source ./set_gopath.sh`
      • Set the MONGOD environment variable to a MongoDB connection string URI for the replica set to test
      • Run `time go test -v ./mongodump -test.types=unit,integration`
      Show
      Install Go (my test used Go 1.9.2) Clone the mongo-tools repo cd into the directory and check out commit 9c973cbf run ` source ./set_gopath.sh ` Set the MONGOD environment variable to a MongoDB connection string URI for the replica set to test Run ` time go test -v ./mongodump -test.types=unit,integration `

      When running the mongodump integration tests, I noticed a significant performance difference between 3.4.10 replica sets (WT) and 3.6.0-rc4 replica sets (both WT and MMAPv1). On my MBP, the difference was 50% to 100%+. On my 20-core desktop, the difference was ~ 18%. The workloads involved are tiny.

        1. output-3.4.10.txt
          8 kB
        2. output-3.6.0-rc4.txt
          8 kB

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            david.golden@mongodb.com David Golden
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: