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

sample_rates.js should use actual traffic instead of target traffic to calculate the expected number of sampled queries

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Sharding NYC 2023-01-09
    • 20
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This test currently doesn't account for actual network conditions. It uses the expected (i.e. target) number of queries per second to calculate the expected number of queries per second. This has caused the actual number of sampled queries to sometimes be very off from the expected as can be seen in BF-26996 and BF-27198. Therefore, the test should use actualNum{Find,Delete,Agg}PerSec instead of the targetNum{Find,Delete,Agg}PerSec to calculate expected{Find,Delete,Agg}Count.

            Assignee:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Reporter:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: