This is a copy-set mode, plus an authentication parameter--authenticationdatabase
Mongostat--port 20012-uadmin-p= ' xxxxx '--authenticationdatabase admin
Explanation of each field:
INSERT/S: The official explanation is the number of objects inserted into the database per second, and if it is slave, there is * before the value, which means the copy set operation
QUERY/S: Number of query operations per second
UPDATE/S: Number of update operations per second
DELETE/S: Number of delete operations per second
GETMORE/S: Getmore operand per second when cursor (cursor) is queried
Command: Number of commands executed per second, two values displayed in master/slave system (e.g. 3|0), sub-table on behalf of local | Copy command
Note: The number of commands executed in one second, such as bulk INSERT, is considered to be a single command (so the meaning should be small)
Dirty: For Wiredtiger engines only, the official website explains the percentage of cache of dirty data bytes
Used: Only for Wiredtiger engines, the official website explains the percentage of cache that is in use
Flushes:
For Wiredtiger engine: refers to the number of triggers of checkpoint during a polling interval
For MMAPV1 Engine: The number of times per second that Fsync data is written to the hard disk
Note: General is 0, intermittent will be 1, by calculating the interval between two 1, you can roughly understand how long to flush once. Flush overhead is great, and if you flush frequently, you might want to find out why.
Vsize: Virtual memory usage, in megabytes (this is the total data that was last called in Mongostat)
Res: Physical memory usage, in megabytes (this is the total data that was last called in Mongostat)
Note: This is the same as what you see with top, vsize generally will not have a big change, res will slowly rise, if the res often suddenly drop, to check if there are other programs crazy eat memory.
QR: Queue length for client to wait for read data from MongoDB instance
QW: The length of the queue that the client waits to write data from a MongoDB instance
AR: Number of active clients performing read operations
AW: Number of live clients performing write operations
Note: 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 really is a heavy load, you need to add the machine
Network incoming traffic for NETIN:MONGODB instances
Network outbound traffic for NETOUT:MONGODB instances
Note: This two fields table name network bandwidth pressure, in general, will not become a bottleneck
Conn: Total number of open connections, is the sum of Qr,qw,ar,aw
Note: MongoDB creates a thread for each connection, the creation and release of threads will also have overhead, so try to properly configure the startup parameters for the number of connections.
mongodb3.2+ Performance Monitoring
