Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-17421

WiredTiger b-tree uses much more memory than wiredTigerCacheSizeGB

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • 3.0.0-rc10
    • None
    • Storage, WiredTiger
    • Fully Compatible
    • ALL
    • Hide

      1. Run iibench-mongodb with 10 insert threads and 1 query thread to insert 400M docs (bash run.simple.bash.q1)
      2. Run iibench-mongodb with 1 insert thread rate limited to 100 docs/second and 10 query threads (bash run.simple.bash.q10)

      Show
      1. Run iibench-mongodb with 10 insert threads and 1 query thread to insert 400M docs (bash run.simple.bash.q1) 2. Run iibench-mongodb with 1 insert thread rate limited to 100 docs/second and 10 query threads (bash run.simple.bash.q10)

    Description

      After running iibench-mongodb with --wiredTigerCacheSizeGB=70 the process size (vsz) was 87G with snappy and 94G with zlib. I don't know yet whether it will continue to grow. Regardless, 1.24X or 1.34X beyond 70G seems like too much when that is an extra 17G and 24G.

      Attachments

        1. jmongoiibench.java
          35 kB
          Mark Callaghan
        2. mongo.conf
          0.5 kB
          Mark Callaghan
        3. o.stat.snappy
          11 kB
          Mark Callaghan
        4. o.stat.zlib
          11 kB
          Mark Callaghan
        5. run.simple.bash.q1
          4 kB
          Mark Callaghan
        6. run.simple.bash.q10
          4 kB
          Mark Callaghan

        Issue Links

          Activity

            People

              michael.cahill@mongodb.com Michael Cahill
              mdcallag Mark Callaghan
              Votes:
              0 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: