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

Decreased throughput due to changes in scheduling algorithm? (mms-prod-pings1)

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.8.0-rc2
    • Component/s: Performance
    • None
    • Fully Compatible

      Please see attached MMS graph showing a time range that shows a particular workload on 2.6.3 and then 2.8.0rc2 (mmapv1). Note that the query opcounters (bright green, highest line) and the update opcounters (lighter green, lower line) both decreased when we upgrade to 2.8.0rc2.

      One significant workload on this replica set has the following hourly pattern:

      • 0-20: "rest"
      • 20-40: do as much work as possible. Lots of updates and reads.
      • 0: bail, even if not done

      You can see the change a bit more clearly in this 5 minute average of just update opcounters:

        1. server16482_queries_per_second.png
          server16482_queries_per_second.png
          45 kB
        2. server16482_worse_case_latencies.png
          server16482_worse_case_latencies.png
          54 kB
        3. throughput.png
          throughput.png
          144 kB
        4. updates.png
          updates.png
          22 kB

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            cailin.nelson@mongodb.com Cailin Nelson (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: