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

YCSB can generate large maximum in-memory page size

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage 2017-10-02, Storage 2017-10-23

      I noticed while analysing some data from a YCSB run that the reported cache: maximum page size at eviction (MB) of 928MB, which is far above the expected value.

      The YCSB 6.0 configuration is:

      fieldcount=10
      fieldlength=10
      recordcount=120000000
      operationcount=100000000
      workload=com.yahoo.ycsb.workloads.CoreWorkload
      readallfields=true
      readproportion=0.5
      updateproportion=0.5
      scanproportion=0
      insertproportion=0
      

      The original test was run on a machine with 256GB of memory, and a 3 disk SSD raid 0 array.

      MongoDB was started with the journal on a separate drive and the following options:

      mongod --wiredTigerEngineConfigString="eviction_dirty_trigger=95,eviction_dirty_target=80"
      

        1. metrics.2017-10-06T00-42-54Z-00000
          250 kB
          Vamsi Boyapati
        2. WiredTigerStat.05.20
          1.19 MB
          Vamsi Boyapati
        3. WiredTigerStat.05.21
          4.02 MB
          Vamsi Boyapati

            Assignee:
            vamsi.krishna@mongodb.com Vamsi Boyapati
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: