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

Significant performance degradation between SA mongod to replica set on insert only workload

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.0.0-rc11
    • Component/s: WiredTiger
    • ALL
    • RPL 1 04/03/15

      v3.0.0-Rc11

      Environment:

      • Replica set with 2 nodes vs. stand alone mongod
      • The measurement has been taken from the same machine, when it was configured as replica set the machine worked as primary.
      • Windows 2012 magnatic drive

      Workload:
      • Used hammer.mongo to do insert only workload

      Measured a signficent amount of performance degrdation between Stand Alone to Replica set

      Measurements Stand alone performance Replica set (2 members) Performance difference
      IO Write throughput 12 K operations/sec 2 K operations/sec -84%
      MongoStat info 15 K inserts/sec 2 K insert/sec ..TBD..
      Context switchs 36 K 4.5K  

      More details @ https://docs.google.com/a/10gen.com/document/d/1RyvsyEs0HygsSZJ1hs_02yWxR-NEzjRNi6jf6I38GSo/edit?usp=sharing

      will work to identify the bottleneck

        1. InsertOnlySAvsReplSetWindows.png
          InsertOnlySAvsReplSetWindows.png
          11 kB
        2. ReplicaSetMember (1).csv
          106 kB
        3. ReplicaSetMemberLog.txt
          121 kB
        4. ReplicaSetMember - MongoStat.txt
          2 kB
        5. SA.csv
          212 kB
        6. SA.txt
          970 kB
        7. Screen Shot 2015-03-18 at 5.13.21 PM.png
          Screen Shot 2015-03-18 at 5.13.21 PM.png
          46 kB
        8. Screen Shot 2015-03-20 at 12.40.47 PM.png
          Screen Shot 2015-03-20 at 12.40.47 PM.png
          23 kB

            Assignee:
            chung-yen.chang Chung-yen Chang
            Reporter:
            eitan.klein Eitan Klein
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: