Investigate ways to bring back performance that was lost due to a correctness fix

XMLWordPrintableJSON

    • Type: Build Failure
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Not Applicable

      New description

      As per luke.pearson@mongodb.com this regression is a result of a correctness change so it could not be rolled back. However, it is interesting that this change resulted in such a massive performance drop, so it might provide useful context for further performance improvements.

      Since the change fixed version cursors, this should be handled by the Foundations team.

      Perf regression old ticket body

      A recent change affecting the wiredtiger evergreen project has potentially caused performance changes to one or more automated performance tests.

      This Perf BF may contain both regressions and improvements with the emphasis being drawn to regressions. On the Perf BF page, you may filter out regressions by selecting the corresponding Change Type (far left) column in the table.

      When closing this ticket, please populate the 'Fix revision' field if appropriate.

            Assignee:
            Unassigned
            Reporter:
            Mongo Perf User
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: