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

Perf regression for workload that updates 1 row with 1 or many clients

    • Product Performance
    • ALL
    • Hide

      I used my fork of jmongosysbench - https://github.com/mdcallag/sysbench-mongodb as my changes have yet to be pushed upstream.

      This is the only option I set for mongod:
      journalCommitInterval=300

      Then I load 400M rows into 1 collection (in the blog post I used 8 collections, but the repro case here only needs 1):
      bash run.sh 1 400000000 1 5 yes no $( date +%s )

      Then I run the test first for one client thread:
      t=10; dop=1; bash run.sh 1 1 $dop $t no yes $( date +%s )

      And then for 32 client threads:
      t=10; dop=32; bash run.sh 1 1 $dop $t no yes $( date +%s )

      Show
      I used my fork of jmongosysbench - https://github.com/mdcallag/sysbench-mongodb as my changes have yet to be pushed upstream. This is the only option I set for mongod: journalCommitInterval=300 Then I load 400M rows into 1 collection (in the blog post I used 8 collections, but the repro case here only needs 1): bash run.sh 1 400000000 1 5 yes no $( date +%s ) Then I run the test first for one client thread: t=10; dop=1; bash run.sh 1 1 $dop $t no yes $( date +%s ) And then for 32 client threads: t=10; dop=32; bash run.sh 1 1 $dop $t no yes $( date +%s )

      My results are at http://smalldatum.blogspot.com/2014/04/biebermarks.html. Using the same hardware for the test and 2.4.9 versus 2.6 (rc2 or release) I get more updates/second with 2.4.9 versus 2.6 – 1.22X more at 32 concurrent clients and 1.11X more updates/second with 1 client.

        1. 249.pdf
          21 kB
        2. 260.pdf
          21 kB
        3. run.sh
          5 kB

            Assignee:
            backlog-server-perf [DO NOT USE] Backlog - Performance Team
            Reporter:
            mdcallag Mark Callaghan
            Votes:
            0 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: