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

Run perf benchmarks as part of release process

    • Type: Icon: Task Task
    • Resolution: Works as Designed
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: Performance
    • None
    • 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?

      Use Case

      As a...user
      I want... the Node driver team to run their benchmarks before doing releases
      So that... I can upgrade without seeing performance degradation

      We got some tickets around performance degradation in 4.0, we likely could have caught this ourselves if we ran the driver benchmark suite prior to releasing.

      As a stopgap we could start doing this manually, but ideally in NODE-1175 we will get these running in Evergreen and will be able to track perf results over time and confirm performance hasn't degraded prior to releases (perhaps in some automated way, related to NODE-1249).

      We could also consider addressing this as part of NODE-3466.

      User Impact

      *What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

      Dependencies

      • upstream and/or downstream requirements and timelines to bear in mind

      Unknowns

      • questions that need to be answered to determine implementation

      Acceptance Criteria

      Implementation Requirements

      • functional reqs, potential snafus to avoid, performance targets, etc

      Testing Requirements

      • unit test, spec test sync, etc

      Documentation Requirements

      • DOCSP ticket, API docs, etc

      Follow Up Requirements

      • additional tickets to file, required releases, etc

            Assignee:
            Unassigned Unassigned
            Reporter:
            kaitlin.mahar@mongodb.com Kaitlin Mahar
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: