[JAVA-4462] Introduce a benchmark that could have sensed JAVA-4452 Created: 31/Jan/22  Updated: 28/Sep/23

Status: Backlog
Project: Java Driver
Component/s: Performance
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Valentin Kavalenka Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by JAVA-4452 Improve performance characteristics o... Closed
Related
related to JAVA-4454 Introduce checking benchmark results ... Closed
related to JAVA-5065 Standardize performance testing infra... Closed

 Description   

The existing driver benchmarks did not sense the JAVA-4452 regression: there is no data before May 18, but based on the Jira tickets that caused JAVA-4452, the commits to master happened on Apr 14, May 1, Jun 8, Sep 27, and I don't see charts having a stair step shape near those dates. We need to have a new implementation of com.mongodb.benchmark.framework.Benchmark that could have sensed JAVA-4452. Once we have it, we may consider filing DRIVERS task to add the benchmark to https://github.com/mongodb/specifications/blob/master/source/benchmarking/benchmarking.rst.


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