Use Case

As a... Node.js engineer
I want... one version of the benchmarks external from the driver
So that... I can compare different driver versions using the same tests

Developer Experience

• having the benchmark history tracked separately from the driver helps us apply fixes and improvements to the benchmarks that can be used across driver versions.

Dependencies

• None

Risks/Unknowns

• None

Acceptance Criteria

Implementation Requirements

• Move benchmarks as is to the tooling repo
• Set up system of fetching the benchmarks from the other repo (npm or git)

Testing Requirements

• Check no significant changes to benchmarks results are observed

Documentation Requirements

• test/readme.md instructions

Follow Up Requirements

• Follow up with benchmark implementation improvements