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

Add throughput probing state metrics

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Workload Scheduling
    • Fully Compatible
    • Workload Scheduling 2025-02-03, Workload Scheduling 2025-02-17

      The throughput probing implementation currently reports the following metrics:

      • timesIncreased
      • totalAmountIncreased
      • timesDecreased
      • totalAmountDecreased
      • resizeDurationMicros

      Adding a few more metrics would help us better diagnose the behavior of throughput probing in tickets like HELP-69090:

      • timesProbedStable: the cumulative number of times the algorithm performed a stable probe
      • timesProbedUp: the cumulative number of times the algorithm probed up
      • timesProbedDown: the cumulative number of times the algorithm probed down

      Note that these metrics are different from timesIncreased and timesDecreased. The existing metrics measure how many times a probe up/down resulted in accepting the new concurrency.

            Assignee:
            dominic.hernandez@mongodb.com Dominic Hernandez (Inactive)
            Reporter:
            vojislav.stojkovic@mongodb.com Vojislav Stojkovic
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: