Insert: Number of inserts in one second
Query: Number of queries in one second
Update: Number of updates in one second
Delete: Number of deletions in one second
Getmore: Getmore operation of cursor at query time
Command: Number of commands executed in one second
Flushes: The number of flush in a second is generally 0, or 1, by calculating the interval between two 1, you can roughly understand how long flush once. Flush overhead is great, and if you flush frequently, you may want to find out why.
Mapped:vsize:res: These three and with top see the same, mapped, vsize generally will not have big changes, res will slowly rise, if res often suddenly drop, to check whether there are other programs crazy eat memory.
Faults: This value is often not 0 under high pressure. If it's often not 0, it's time to add memory.
Locked:mongodb is a read-write lock, which refers to the percentage of time that a write lock lives. This value is too large (often more than 10%), that is the situation.
DX MISS: Very important parameter, under normal circumstances, all queries should be indexed, that is, the idx miss is 0. If the value here is large, the index is missing.
Qr|qw:queue lengths for clients Waiting (Read|write)
Ar|aw:active Clients (Read|write)
If these two values are large, then the DB is blocked and the DB processing speed is less than the requested speed. See if there is a lot of slow queries that are expensive. If the query is all right, it is really a heavy load, you need to add the machine.
Netin:network Traffic In-bits
Netout:network Traffic Out-bits
Network bandwidth pressure
Conn:mongodb creating a thread for each connection, the creation and release of threads are also overhead. Try not to make this a large number.
REPL: Server Current state
M-master
Sec-secondary
Rec-recovering
Unk-unknown
Slv-slave
Time: Current
This article is from "someone who says I am a tech house" blog, please be sure to keep this source http://1992mrwang.blog.51cto.com/3265935/1585636
MongoDB self-monitoring Mongostat numerical description