Uploaded image for project: 'Python Driver'
  1. Python Driver
  2. PYTHON-4350

Faster and more consistent performance benchmark execution times

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Unknown Unknown
    • 4.7
    • Affects Version/s: None
    • Component/s: None
    • None
    • Python Drivers
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      We have a few problems with the perf benchmarks. First they take an enormous amount of time to run, both locally and on Evergreen. The most recent build took 42 minutes. This excessive time makes it take longer to investigate performance issues.

      A second issue is that some of the individual benchmarks run in a few seconds while others take 5 minutes. We should standardize this so that all the benchmarks run in a similar time frame. For example in the most recent build, TestSmallDocBulkInsert and TestGridFsDownload both took 8 seconds while TestFindOneByID took 5 minutes. This could explain why some benchmark appear less stable and have more run-to-run variance than others.

      I propose we make each benchmark run for a minimum of 30 seconds and a maximum of 60.

            Assignee:
            shane.harvey@mongodb.com Shane Harvey
            Reporter:
            shane.harvey@mongodb.com Shane Harvey
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: