Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-4462

Introduce a benchmark that could have sensed JAVA-4452

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Performance
    • Labels:

      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.

            Unassigned Unassigned
            valentin.kovalenko@mongodb.com Valentin Kavalenka
            0 Vote for this issue
            1 Start watching this issue