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

Throughput degradation with j:true after restart of mongod

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.0-rc0
    • Component/s: Storage
    • Labels:
      None
    • ALL

      Test consists of 20 threads inserting empty documents with j:true:

      function run() {
          for (i = 0; i < 10000; i++)
              db.c.insert({}, {writeConcern: {j: true}})
      }
      

      Throughput after the first and subsequent restarts of mongod is about 40% lower than throughput on the initial startup of mongod. (First run below was on 3.4.9 and second was on 3.6.0-rc0, but it turned out that was not the important difference, it was the restart that reduced performance, on all versions tested).

        1. jtrue.png
          jtrue.png
          62 kB
        2. disk.png
          disk.png
          137 kB
        3. Screen Shot 2017-10-16 at 2.55.31 pm.png
          Screen Shot 2017-10-16 at 2.55.31 pm.png
          31 kB
        4. metrics.349_3
          22 kB
        5. metrics.360_3
          25 kB
        6. 349_fresh
          22 kB
        7. 360_restart
          27 kB
        8. 349_restart
          25 kB
        9. 360_fresh
          24 kB
        10. jtrue2.png
          jtrue2.png
          123 kB

            Assignee:
            sue.loverso@mongodb.com Susan LoVerso
            Reporter:
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            17 Start watching this issue

              Created:
              Updated:
              Resolved: