Investigate 14% regression in mixed_findOne from telemetry

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      task test measurement arguments z_score % change % change (stable) % change (stable to stable) evergreen_baseline_result evergreen_test_result
      mixed_workloads mixed_findOne ops_per_sec {'thread_level': 512} -2.176434757 -15.40414 -12.38781578 -14.68251591 https://evergreen.mongodb.com/task/sys_perf_linux_1_node_replSet.2022_11_mixed_workloads_17965f587025e0c7dad82e396fd0d7746f92b187_23_03_29_23_14_09 https://evergreen.mongodb.com/task/sys_perf_linux_1_node_replSet_telemetry_mixed_workloads_17965f587025e0c7dad82e396fd0d7746f92b187_23_03_29_23_14_09

      Investigate or fix - when we turn the flag on in master, all > 10% regressions with z_scores > 2 will trigger automatic BF creation. This test failure has > 10% regression and >2.0 z_score.

       

            Assignee:
            [DO NOT USE] Backlog - Query Integration
            Reporter:
            Colby Ing
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: