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

17% throughput regression in insert workload

    XMLWordPrintable

Details

    • Bug
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • 3.6.0
    • None
    • Storage, Write Ops
    • None
    • Storage 2017-11-13, Storage 2017-12-04, Storage 2018-01-29, Repl 2018-02-26, Repl 2018-03-12, Repl 2018-03-26
    • 0

    Description

      Simple insert workload:

          res = benchRun({
      		 
              ops: [
      		 
                  {op: "insert", doc: {},  ns: "test.c"},
      		 
              ],
      		 
              seconds: 45,
      		 
              parallel: 15
      		 
          })
      		 
          printjson(res)

      standalone shows ~11% throughput reduction

      3.4.9:     "totalOps/s" : 312257.31243007537,
      		 
      3.6.0-rc0  "totalOps/s" : 277214.2306740861,

      1-node replica set shows ~50% throughput reduction

      3.4.9:     "totalOps/s" : 181808.21357151057,
      		 
      3.6.0-rc0  "totalOps/s" : 91202.31599375796,

      Metrics for the 1-node replica set case suggest issue may be related to large number of write-lock calls, about 3 per insert:

      Attachments

        1. ensure-session.patch
          2 kB
        2. pmp.out.3513
          17 kB
        3. pmp.out.359
          8 kB
        4. pmp.patch.sesscache
          12 kB
        5. run2.png
          run2.png
          127 kB

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31902 Reduce contention on ShardingState::_mutex for insert workloads

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-31879 remove extraneous synchronization in oplog

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-31882 For vectored inserts, start transaction prior to assigning first timestamp

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-31899 Improve getTerm() performance

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-31912 waitUntilDurable() should use its own WT_SESSION, not one from the cache

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-34604 low performance under 3.6.4 with wiredTiger storage

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-40250 High contention for ReplicationCoordinatorImpl::_mutex in w:majority workloads

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-59776 50% regression in single multi-update

          • Major - P3 - Major loss of function.
          • Closed

          Question - SERVER-34562 I use YCSB testing comparise mongodb3.6.3 with mongodb3.4.13 ,find the mongodb3.4.13 insert and update performance is one and a half times than mongodb3.6.3

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              Votes:
              3 Vote for this issue
              Watchers:
              45 Start watching this issue

              Dates

                Created:
                Updated: