Uploaded image for project: 'Evergreen'
  1. Evergreen
  2. EVG-15868

Move newly exposed configurations to separate collection

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • None
    • current_quarter
    • app
    • None

    Description

      Currently in this project, in many instances it is necessary to retrieve the most recent valid config when a version is not explicitly provided.  This requires a lookup of all parser projects associated with a project, sorting them by revision number and taking the most recent one to apply its configuration.  This database operation is expensive since some projects have a large number of parser project versions accrued over time.  This has been shown to put stress on evergreen in production since this is looked up very frequently in the codebase:

      https://jira.mongodb.org/browse/EVG-15856

      Instead, we can store the newly supported config properties as a different struct in a different collection.  These configs can be derived from the same yaml file that generates the parser project, and will be less prone to long lists of version history than the parser projects (since they often contain long lists of task/variant data). This will also allow us to directly look up the configurations instead of what we currently do, which is make a DB call to get the most recent version, and then use that version to make another DB query to retrieve its parser project.

      Attachments

        Issue Links

          Activity

            People

              malik.hadjri@mongodb.com Malik Hadjri
              malik.hadjri@mongodb.com Malik Hadjri
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: