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

InMemory engine: 'inMemorySizeGB' doesn't limit the process memory usage

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 3.2.15
    • Component/s: Internal Code, Performance, Stability
    • Labels:
      None
    • ALL
    • Hide

      Start in memory mongod process using:
      /usr/bin/mongod --storageEngine inMemory --inMemorySizeGB 2 --quiet --config /etc/mongod.conf

      Create enough DBs to make the process memory higher than 2GB.

      Show
      Start in memory mongod process using: /usr/bin/mongod --storageEngine inMemory --inMemorySizeGB 2 --quiet --config /etc/mongod.conf Create enough DBs to make the process memory higher than 2GB.

      Using MongoDB Enterprise v3.2.15 on Ubuntu 16.04
      Starting mongod as a service using:
      /usr/bin/mongod --storageEngine inMemory --inMemorySizeGB 2 --quiet --config /etc/mongod.conf

      It seems that the memory limit doesn't really limit the process memory, mongod process could take more than 3GB of memory.

      Note that on our implementation we work with few hundreds of DBs.
      Specifically our auto tests creates a large amount of databases and drop them after the test ends. However the memory isn't released.

      Also after a while the process start to take ~100% CPU even without any client load.

      Thanks,
      Assaf

        1. IFfwJD.png
          IFfwJD.png
          135 kB
        2. stacks.png
          stacks.png
          80 kB

            Assignee:
            mark.agarunov Mark Agarunov
            Reporter:
            assaf@xmcyber.com Assaf Oren
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: