MongoDB MMAPv1 Details
Docs per second inserted, updated, deleted or returned. Also showing replicated write ops and internal TTL index deletes.
Time spent per second waiting to acquire locks.
Unix or Window memory page faults. Not necessarily from mongodb.
MB processed through the journal in memory.
MB committed to disk for the journal.
Average time in ms, over full uptime of mongod process, the MMAP background flushes have taken.
Queue size of ops waiting to be submitted to storage engine layer. (N.b. see WiredTiger concurrency tickets for number of ops being processed simultaneously in storage engine layer.)
Ops and Replicated Ops/sec, classified by legacy wire protocol type (query, insert, update, delete, getmore).
This panel shows the number of objects (both data (scanned_objects) and index (scanned)) as well as the number of documents that were moved to a new location due to the size of the document growing. Moved documents only apply to the MMAPv1 storage engine.
- Page updated 2020-11-23