Use Case

As a... driver engineer
I want... to have driver performance benchmark tests running in the CI
So that... I have a consistent environment in which to compare the effects of ongoing work

User Impact

• Reliable performance

Dependencies

• None

Unknowns

• Open question: utf8 validation -> do we want 2 configurations?

Acceptance Criteria

• Run the tests in evergreen in some configuration
  • Make sure the output in the logs is meaningful
• Using evergreen tools is optional, look into alerting, create follow up tickets for identified actionable items (reporting, comparing against previous runs)
  • Dev note: refer to BSON etc/benchmarks/lib_runner.js

Implementation Requirements

• We are currently missing the parallel spec data files and testing (and legacy bson - though that might not be needed)
  • Add it, or add a note about why it is not needed
• We should also update our implementation of existing benchmark to use more modern methods (we should investigate if perf hooks would work well here), some of the currently used apis are marked legacy/deprecated e.g. `process.hrtime`
  • Research the appropriate methods to use and implement them, e.g. performance.now

Testing Requirements

• This is a ticket for tests

Documentation Requirements

• None

Follow Up Requirements

• File follow up tickets as they come up