Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-6776

Provide benchmark results from basic run of eMRCf testing

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      Using the tools created for WT-6662, et al., run a test to measure the performance impact of history store growth in a degraded PSA replica set and present the results here.

      The goal is to describe the basic test and the numbers I get when running a modest size instance of the test.  Based on feedback we can adjust what the test does and expend the data set and runtime to potentially stress the system more.

      Because this ticket is intended as an exposition of results, I am revising my comments as I figure things out, rather than having a string of comments that correct and clarify previous ones. 

      [Update: I was misinterpreting results from Genny—measurements I thought were in microseconds were really in nanoseconds.  Since the comments here are more of a report than a conversation, I'm going to go back and edit them to present the correct values.]

        1. insert.jpg
          insert.jpg
          33 kB
        2. Slowdown.jpg
          Slowdown.jpg
          32 kB
        3. insert example.jpg
          insert example.jpg
          36 kB
        4. insert_tail.jpg
          insert_tail.jpg
          39 kB
        5. readmostly.jpg
          readmostly.jpg
          45 kB
        6. updateheavy.jpg
          updateheavy.jpg
          46 kB
        7. delete.jpg
          delete.jpg
          35 kB
        8. delete-slow-tail.jpg
          delete-slow-tail.jpg
          34 kB
        9. delete-slow.jpg
          delete-slow.jpg
          36 kB

            Assignee:
            keith.smith@mongodb.com Keith Smith
            Reporter:
            keith.smith@mongodb.com Keith Smith
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: