[CSHARP-4670] Implement Drivers Performance Benchmarking Testing Specification Created: 07/Jun/23  Updated: 13/Jan/24  Resolved: 13/Jan/24

Status: Closed
Project: C# Driver
Component/s: Performance, Performance Benchmarking
Affects Version/s: None
Fix Version/s: 2.24.0

Type: New Feature Priority: Unknown
Reporter: Patrick Gilfether Assignee: Adelin Mbida Owona
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by DRIVERS-301 Driver Performance Benchmarking Closed
is depended on by DRIVERS-385 Port Driver Benchmark Tests to Evergreen Implementing
is depended on by CSHARP-4713 Standardize performance testing infra... Closed
Duplicate
is duplicated by CSHARP-2085 Port Driver Benchmark Tests to Evergreen Closed
is duplicated by CSHARP-1829 Concurrency benchmark unable to utili... Closed
is duplicated by CSHARP-3999 Introduce performance benchmarks in EG Closed
Related
is related to DRIVERS-2666 Standardize performance testing infra... Implementing
Quarter: FY24Q3
Documentation Changes Summary:

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?


 Description   

Summary

  • Implement Driver Performance Benchmarking specification
  • Port tests to Evergreen

Motivation

As of Q2 2023, MongoDB Product and Engineering leadership is placing increasing priority upon improving end-to-end performance within drivers. The Driver Benchmarking spec provides an internal set of benchmarking standards already implemented by many drivers. By implementing these tests and including them in our Evergreen suite, we will be able to meaningfully track C# driver performance over time, catching performance regressions and improvements in new builds. Further, because other drivers have adopted these tests, we will have some comparison benchmarks available (most comparable will be Java).

Who is the affected end user?

DBX Engineers, PMs, business stakeholders

How does this affect the end user?

no direct impacts, however monitoring performance will allow us to ship fewer performance regressions and better identify performance improvements.

How likely is it that this problem or use case will occur?

We will need to adopt some solution for benchmarking in order to measure and report progress.

Is this issue urgent?

Ideally, in Q3FY2024

Is this ticket required by a downstream team?

Not at the moment.

Is this ticket only for tests?

Yes.

Acceptance Criteria

  • Drivers Benchmarking Spec implemented
  • Tests deployed on Evergreen and monitored with alerting in all builds.

Generated at Wed Feb 07 21:48:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.