Recover performance regressions due to timestamps

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • Storage Non-NYC 2018-05-21
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      A number of replica set performance tests showed regressions with the MongoDB 3.6 release due to enabling read concern majority. Some of these regressions were due to WiredTiger being required to keep more content in cache, and the implementation of an external transaction ID manager (timestamps).

      We need to re-run those workloads and make changes to return performance to previous levels where it's practical.

            Assignee:
            Alexander Gorrod
            Reporter:
            Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: