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

Migrate uses of json.send to perf.send in Evergreen project YAML

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.4.0
    • None
    • Hide

      DRIVERS-1892:
      As of PM-2172, the TIPS team would like to remove its legacy performance gathering and analysis API in favor of a new, more robust option. In order to migrate to the new API, uses of json.send in Evergreen project YAML should be removed in favor of using perf.send (assuming it is desirable to continue to maintain / run the testing that uses json.send) . Please see the linked DRIVERS ticket for detailed information about how to use perf.send. We have also added docs for migrating away from json.send and onto perf.send.

      Show
      DRIVERS-1892: As of PM-2172, the TIPS team would like to remove its legacy performance gathering and analysis API in favor of a new, more robust option. In order to migrate to the new API, uses of json.send in Evergreen project YAML should be removed in favor of using perf.send (assuming it is desirable to continue to maintain / run the testing that uses json.send) . Please see the linked DRIVERS ticket for detailed information about how to use perf.send. We have also added docs for migrating away from json.send and onto perf.send.

    Description

      Summary

      As of PM-2172, the TIPS team would like to remove its legacy performance gathering and analysis API in favor of a new, more robust option. In order to migrate to the new API, uses of json.send in Evergreen project YAML should be removed in favor of using perf.send (assuming it is desirable to continue to maintain / run the testing that uses json.send) . The following instructions describe how to use perf.send. We have also added docs for migrating away from json.send and onto perf.send.

      Motivation

      Who is the affected end user?

      This ticket tracks the mongo-python-driver-perf change specifically.

      How does this affect the end user?

      The trend charts UI will continue to display any legacy performance data that had previously been gathered with json.send even after migration to perf.send. Additionally, it appears that change points are not presently being detected for these projects even in cases where performance data is being collected; migration to perf.send should avoid these sorts of errors.

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

      N/A

      If the problem does occur, what are the consequences and how severe are they?

      N/A

      Is this issue urgent?

      TIPS would like to remove the json.send tooling as part of PM-2172, which we are working on this quarter. If all the usages could be removed or migrated to the new tooling by October 25th, that would be great.

      Is this ticket required by a downstream team?

      Yes. It is required by TIPS for PM-2172.

      Is this ticket only for tests?

      Yes. This is specific to gathering and analyzing performance data.

      Attachments

        Activity

          People

            jeff.yemin@mongodb.com Jeffrey Yemin
            maria.vankeulen@mongodb.com Maria van Keulen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: