I am trying to understand the results of mongostat: example <pre class="prettyprint"><code>insert query update delete getmore command flushes mapped vsize res faults locked % idx 0 2 4 0 0 10 0 976m 2.21g 643m 0 0.1 0 0 1 0 0 0 4 0 976m 2.21g 643m 0 0 0 0 0 0 0 0 1 0 976m 2.21g 643m 0 0 0 </code></pre> I see <pre class="prettyprint"><code>mapped - 976m vsize-2.2.g res - 643m </code></pre> <ul> <li> <code>res</code> - RAM, so ~650MB of my database is in RAM</li> <li> <code>mapped</code> - total size of database (via memory mapped files)</li> <li> <code>vsize</code> - ???</li> </ul> not sure why vsize is important or what exactly it means in this content - im running an m1.large so i have like 400GB of HD space + 8GB of RAM. Can someone help me out here and explain if <ol> <li>I am on the right page</li> <li>what stats I should monitor in production</li> </ol>

Also you can use these mini tools watching mongodb http://openmymind.net/2011/9/23/Compressed-Blobs-In-MongoDB/ by the way I remembered this great online tool from 10gen https://mms.10gen.com/user/login

Understanding results of mongostat

Tags:

mongodb

scalability

nosql

ubuntu

production

I am trying to understand the results of mongostat:

example

insert  query update delete getmore command flushes mapped  vsize    res faults locked % idx  
0      2      4      0       0      10       0   976m  2.21g   643m      0      0.1          0       
0      1      0      0       0       4       0   976m  2.21g   643m      0        0          0       
0      0      0      0       0       1       0   976m  2.21g   643m      0        0          0

I see

mapped - 976m
vsize-2.2.g
res - 643m

res - RAM, so ~650MB of my database is in RAM
mapped - total size of database (via memory mapped files)
vsize - ???

not sure why vsize is important or what exactly it means in this content - im running an m1.large so i have like 400GB of HD space + 8GB of RAM.

Can someone help me out here and explain if

I am on the right page
what stats I should monitor in production

815

asked Dec 22 '11 02:12

josephmisiti

2 Answers

Also you can use these mini tools watching mongodb

http://openmymind.net/2011/9/23/Compressed-Blobs-In-MongoDB/

by the way I remembered this great online tool from 10gen

https://mms.10gen.com/user/login

answered Oct 13 '22 01:10

halil

This should give you enough information

mapped       - amount of data mmaped (total data size) megabytes
vsize        - virtual size of process in megabytes
res          - resident size of process in megabytes