Use Case

As a Node.js MongoDB contributor
I want to validate performance improvements and enter the results into the tracking systems in CI
So that a performance improvement is maintained and does not regress

User Experience

• What is the desired/expected outcome for the user once this ticket is implemented?
  • Contributors can easily add testing to demonstrate improvements and expect the project to maintain the improvement there after
• If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?
  • N/A

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind
  • Uses perf.send, notifications can be figured out later, tracking will be added here.

Risks/Unknowns

• What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
  • None, test only.
• Is there an opportunity for better cross-driver alignment or testing in this area?
  • No
• Is there an opportunity to improve existing documentation on this subject?
  • No

Acceptance Criteria

Implementation Requirements

• Add benchmarking for code in the BSON library not related to serialize/deserialize (helpers, constructors, etc.)

Testing Requirements

• Ensure perf.send works after the task completes and that trend charts will be generated

Documentation Requirements

• None

Follow Up Requirements

• Consider if we need alerting for this.
  • Likely not, I think the value provided here is something we can now check when we're merging new changes.