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

Introduce a benchmark that could have sensed JAVA-4452

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Performance
    • None

    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.

      Attachments

        Issue Links

          is caused by

          Improvement - An improvement or enhancement to an existing feature or task. JAVA-4452 Improve performance characteristics of the connection pool to be on par with the driver 4.2.0

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed
          related to

          Task - A task that needs to be done. JAVA-4454 Introduce checking benchmark results as part of the release process

          • Unknown - Priority not determined yet.
          • Backlog

          Activity

            People

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

              Dates

                Created:
                Updated: