Throughput degradation with j:true after restart of mongod

XMLWordPrintableJSON

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

      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
          62 kB
          Bruce Lucas
        2. disk.png
          137 kB
          Bruce Lucas
        3. Screen Shot 2017-10-16 at 2.55.31 pm.png
          31 kB
          Vamsi Boyapati
        4. metrics.349_3
          22 kB
          Vamsi Boyapati
        5. metrics.360_3
          25 kB
          Vamsi Boyapati
        6. 349_fresh
          22 kB
          Vamsi Boyapati
        7. 360_restart
          27 kB
          Vamsi Boyapati
        8. 349_restart
          25 kB
          Vamsi Boyapati
        9. 360_fresh
          24 kB
          Vamsi Boyapati
        10. jtrue2.png
          123 kB
          Bruce Lucas

            Assignee:
            Susan LoVerso (Inactive)
            Reporter:
            Bruce Lucas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            17 Start watching this issue

              Created:
              Updated:
              Resolved: