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

Enable signal processing (or red/green) checks for Google Microbenchmark

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Blocker - P1 Blocker - P1
    • 5.3.0
    • None
    • Testing Infrastructure
    • None
    • Fully Compatible
    • STM 2022-01-24
    • 2

    Description

      Tasks: https://evergreen.mongodb.com/waterfall/mongodb-mongo-master?task_filter=benchmark

      Context

      As a database contributor

      when I run a patch build containing Google Microbenchmarks

      Then I expect to see red/green results(or async signal processed BFs), as a way to alert me to performance regressions

      AC

      • Ensure signal processing is running in google benchmarks
      • Check historical values for google benchmarks through the evergreen API of the base commit¬†
      • Make the threshold configurable in a yaml file in google benchmarks
        • we'll use 20% for this use case, meaning if the task is 20% worse for Latency (since google benchmarks only reports latency) than the baseline commit then the task will be marked failed (red)
        • The key in the yaml file should be the key for the metric in the json perf output

      Attachments

        Activity

          People

            mikhail.shchatko@mongodb.com Mikhail Shchatko
            cristopher.stauffer@mongodb.com Cristopher Stauffer
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: