File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change 410
410
411
411
.. status:: mem.virtual
412
412
413
- :status:`mem.virtual` displays the quantity, in Mb , of virtual memory
413
+ :status:`mem.virtual` displays the quantity, in megabytes (MB) , of virtual memory
414
414
used by the :program:`mongod` process. In typical deployments this value
415
415
is slightly larger than :status:`mem.mapped`. If this value is
416
416
significantly (i.e. gigabytes) larger than :status:`mem.mapped`,
@@ -429,15 +429,15 @@ mem
429
429
.. status:: mem.mapped
430
430
431
431
The value of :status:`mem.mapped` provides the amount of mapped memory,
432
- in Mb , by
432
+ in megabytes (MB) , by
433
433
the database. Because MongoDB uses memory-mapped files, this value
434
434
is likely to be to be roughly equivalent to the total size of your
435
435
database or databases.
436
436
437
437
.. status:: mem.mappedWithJournal
438
438
439
439
:status:`mem.mappedWithJournal` provides the amount of
440
- mapped memory, in Mb , including the memory used for
440
+ mapped memory, in megabytes (MB) , including the memory used for
441
441
journaling.
442
442
This value will always be twice the value of :status:`mem.mapped`.
443
443
This field is only included if journaling is enabled.
You can’t perform that action at this time.
0 commit comments