Uploaded image for project: 'MongoDB Database Tools'
  1. MongoDB Database Tools
  2. TOOLS-37

mongostat --all reports incorrect value for non-mapped size

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: Legacy C++ Implementation
    • Component/s: mongostat
    • None
    • Environment:
      OS X

      ps reports vsz 28.52 GB

      mms reports
      virtual 28.52
      mapped 13.02
      non-mapped 2.47

      mongostat reports
      vsize 28.5g
      mapped 13.0g
      non-mapped 15.5g <--- believe this is wrong

      Believe that MMS has it right as there is no reason for non-mapped memory in this test to be 15.5 GB. Possibly mongostat is computing non-mapped as vsize-mapped instead of vsize-2*mapped?

            Assignee:
            gabriel.russell@mongodb.com Gabriel Russell (Inactive)
            Reporter:
            ian@mongodb.com Ian Whalen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: