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

Understand reason for perf changes with changing wtperf defaults

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      WT-6081 changed the wtperf table config defaults from:
      "key_format=S,value_format=S,type=lsm,exclusive=true, allocation_size=4kb,internal_page_max=64kb,leaf_page_max=4kb, split_pct=100"
      to
      "key_format=S,value_format=S,type=file,exclusive=true, leaf_value_max=64MB,memory_page_max=10m,split_pct=90,checksum=on"

      This caused changes to perf report we get from Jenkins. This ticket is to understand the reason behind these perf changes and to make sure that it falls under our expectation.

      Here is the summary of major changes to investigate:

      • medium-btree throughput read went down by appx 70%
      • update-btree throughput read seems to have gone down too
      • update-btree throughput update went down by appx 65%
      • update-only-btree throughput went up by appx 75%
      • evict-btree throughput read went down by appx 70%
      • evict-lsm throughput read went down by appx 50%
      • latency warnings in the perf tests have doubled
      • multi-btree-zipfian throughput read went down by appx 50%

      Graphs attached for reference.

        1. wt-perf-btree.png
          wt-perf-btree.png
          435 kB
        2. wt-perf-evict.png
          wt-perf-evict.png
          184 kB
        3. wt-perf-stress.png
          wt-perf-stress.png
          106 kB

            Assignee:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Reporter:
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: