[DOCS-4489] Need clarification on how to read memory statistics in the UNIX top command Created: 09/Dec/14  Updated: 30/Oct/23  Resolved: 15/Oct/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Ronan Bohan Assignee: Andrew Feierabend (Inactive)
Resolution: Won't Fix Votes: 0
Labels: bite-sized
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 4 years, 17 weeks, 1 day ago
Epic Link: DOCSP-1769
Story Points: 0.25

 Description   

Source : http://docs.mongodb.org/manual/faq/diagnostics/#how-do-i-read-memory-statistics-in-the-unix-top-command

How do I read memory statistics in the UNIX top command
Because mongod uses memory-mapped files, the memory statistics in top require interpretation in a special way. On a large database, VSIZE (virtual bytes) tends to be the size of the entire database. If the mongod doesn’t have other processes running, RSIZE (resident bytes) is the total memory of the machine, as this counts file system cache contents.

The description of RSIZE is not completely accurate. It can be the total memory size of the machine (less a small fraction) but only if various conditions are met, e.g. workload (read vs write), readahead settings, etc. It is not, however, accurate to state that it counts the file system cache contents as there are cases when data can be in RAM but not accounted for by the mongod process (due to the memory mapping and remapping behavior in the kernel)



 Comments   
Comment by Andrew Feierabend (Inactive) [ 15/Oct/19 ]

This FAQ regarding top is no longer part of this page.

Generated at Thu Feb 08 07:48:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.