[DRIVERS-301] Driver Performance Benchmarking Created: 27/Apr/16  Updated: 07/Jun/23  Resolved: 02/Mar/17

Status: Closed
Project: Drivers
Component/s: Performance, Performance Benchmarking
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Unassigned
Resolution: Done Votes: 0
Labels: newdriver
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on CDRIVER-1212 C Driver Performance Benchmarking Closed
depends on JAVA-2649 Implement driver benchmarking specifi... Closed
depends on MOTOR-108 Standard driver benchmark suite Closed
depends on RUST-165 Driver Performance Benchmarking Closed
depends on CSHARP-4670 Implement Drivers Performance Benchma... Closed
depends on NODE-1352 Driver Performance Benchmarking Closed
depends on RUBY-2998 Update benchmark suite and verify it ... Closed
Related
related to DRIVERS-385 Port Driver Benchmark Tests to Evergreen Implementing
Driver Compliance:
Key Status/Resolution FixVersion
CDRIVER-1212 Done
MOTOR-108 Done 0.7
NODE-1352 Fixed 3.1.0
JAVA-2649 Fixed
RUST-165 Fixed 0.9.0-alpha
SWIFT-478 Done
RUBY-2998 Fixed 2.18.0
CSHARP-4670 Done 2.24.0

 Description   

Driver performance will be measured by the MongoDB Driver Performance Benchmark (AKA “DriverBench”). It will provide both "horizontal" insights into how individual language driver performance evolves over time and "vertical" insights into relative performance of different drivers.

We do expect substantial performance differences between language families (e.g. static vs. dynamic or compiled vs. virtual-machine-based). However we still expect "vertical" comparison within language families to expose outlier behavior that might be amenable to optimization.

 

UPDATE: Spec is here: MongoDB Driver Performance Benchmark


Generated at Thu Feb 08 08:21:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.