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

WiredTiger b-tree uses much more memory than wiredTigerCacheSizeGB

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.0.0-rc10
    • Component/s: 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)

      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.

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

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

              Created:
              Updated:
              Resolved: