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

20% drop in Update perf for MMAPv1 vs 2.6 MMAP

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.0.0-rc11
    • Component/s: MMAPv1
    • Storage Execution
    • ALL
    • Hide

      /home/ec2-user/mongodb-linux-x86_64-3.0.0-rc11/bin/mongod --dbpath /data2/db --logpath /data3/logs/db/simple_update_mms/server.log --fork --syncdelay 14400 --storageEngine=mmapv1 --bind_ip 127.0.0.1

      python benchrun.py -f testcases/simple_update_mms.js -t 12 14 16 -l SERVER-17342-2-3.0.0-rc11-mmapv1-c1 --rhost "54.191.70.12" --rport 27017 -s /home/ec2-user/mongo-perf-shell/mongo --writeCmd true --tria
      lCount 7 --trialTime 20 --testFilter \'update\' -c 1 --dyno

      Show
      /home/ec2-user/mongodb-linux-x86_64-3.0.0-rc11/bin/mongod --dbpath /data2/db --logpath /data3/logs/db/simple_update_mms/server.log --fork --syncdelay 14400 --storageEngine=mmapv1 --bind_ip 127.0.0.1 python benchrun.py -f testcases/simple_update_mms.js -t 12 14 16 -l SERVER-17342 -2-3.0.0-rc11-mmapv1-c1 --rhost "54.191.70.12" --rport 27017 -s /home/ec2-user/mongo-perf-shell/mongo --writeCmd true --tria lCount 7 --trialTime 20 --testFilter \'update\' -c 1 --dyno

      Problem

      This may be a more general case of SERVER-17342, but there appears to be a general drop on all mongo-perf Update tests in the order of 10-20%. This occurs on contested and uncontested updates, large and small document updates etc.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            alvin Alvin Richards (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved: