Skip to content

Commit 8f1124a

Browse files
author
Ed Costello
committed
DOCS 741 change to megabytes/ MB from Mb
1 parent 16935f9 commit 8f1124a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

source/reference/server-status.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -410,7 +410,7 @@ mem
410410

411411
.. status:: mem.virtual
412412

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
414414
used by the :program:`mongod` process. In typical deployments this value
415415
is slightly larger than :status:`mem.mapped`. If this value is
416416
significantly (i.e. gigabytes) larger than :status:`mem.mapped`,
@@ -429,15 +429,15 @@ mem
429429
.. status:: mem.mapped
430430

431431
The value of :status:`mem.mapped` provides the amount of mapped memory,
432-
in Mb, by
432+
in megabytes (MB), by
433433
the database. Because MongoDB uses memory-mapped files, this value
434434
is likely to be to be roughly equivalent to the total size of your
435435
database or databases.
436436

437437
.. status:: mem.mappedWithJournal
438438

439439
: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
441441
journaling.
442442
This value will always be twice the value of :status:`mem.mapped`.
443443
This field is only included if journaling is enabled.

0 commit comments

Comments
 (0)