Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-6351

Measure performance of current branch by default when benchmarking in BSON CI

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: CI
    • 2
    • Not Needed
    • Hide

      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.

      Show
      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.
    • Not Needed

      Use Case

      As a DBX Node.js engineer,

      I would like the results from a PRs automatic patch to show the performance of the current changes to the code,

      so that I can tell if a change has a negative impact before merging rather than having to run the benchmarks myself modifying variables to do so

      User Experience

      None.

      Dependencies

      None.

      Risks/Unknowns

      None.

      Acceptance Criteria

      Implementation Requirements

      • Update task name to remove nodejs runtime version
      • Modify the bson-bench runner to output environment-agnostic test names and results by default.
      • Ensure that the bson-bench runner can be configured to name tests / test output in a way that includes environment information.  This is useful when comparing across branches locally or across bson versions, etc.
      • Modify js-bson's performance tests in CI to test against the current branch instead of `main`.

      Testing Requirements

      • Manually ensure that all tests still run (with the new names)

      Documentation Requirements

      None.

      Follow Up Requirements

      • N/A

            Assignee:
            durran.jordan@mongodb.com Durran Jordan
            Reporter:
            bailey.pearson@mongodb.com Bailey Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: