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

Performance degradation 3.4.2 vs 3.2.11

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • 3.4.2
    • WiredTiger
    • None
    • ALL

    Description

      Hello,

      We have a rather large mongo replica set containing 19,000 dbs. We have an outstanding issue with wiredTiger cache as per https://jira.mongodb.org/browse/SERVER-27700 and https://jira.mongodb.org/browse/SERVER-27753.

      As we are expecting the change to be in the next 3.4.x-rc we upgraded our cluster from 3.2.11 to 3.4.2 to understand the current performance characteristics and hope that we would gain some improvement.

      Since the upgrade (less than 24 hours) our jobs (which use this cluster) are now taking many hours to finish. In fact some of them have not finished running and we have canceled them.

      The following a screen shot of job run times and how mongo 3.2.11 / 3.4.2 impacts the run time.

      Please can you provide an upload link and I will provide the diagnostic data for the cluster.

      Kind regards,
      Luke

      Attachments

        1. event.png
          event.png
          426 kB
        2. Screen Shot 2017-03-21 at 09.49.22.png
          Screen Shot 2017-03-21 at 09.49.22.png
          74 kB

        Activity

          People

            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            lukemorfitt Luke Morfitt
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: