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