Detailed explanation of mongodb running state parameters

Today, the editor will bring you an article on the introduction of parameters in the running state of mongodb. The editor thinks it's pretty good, so I'll share it for you as a reference. Let's follow the editor and have a look.

Inserts/s inserts per second

Number of queries per second by query/s

Update/s updates per second

Number of delete/s deletions per second

Getmore/s executes getmore per second

Command/s has more commands per second than the above inserts, searches, updates and deletions, and counts other commands.

The number of times per second that flushs/s executes fsync to write data to the hard disk.

The amount of data that is mmap in mapped/s, in MB.

Vsize virtual memory usage (in MB)

Res physical memory usage (in MB)

The number of faults/s access failures per second (only Linux has), and the data is swapped out of physical memory and put into swap. Do not exceed 100. otherwise, the machine memory is too small, resulting in frequent swap writes. At this point, you need to upgrade memory or expand

The percentage of time locked% is locked up, try to keep it below 50%.

Percentage of idx miss% index misses. If it is too high, consider whether there is a lack of indexes.

Q t | r | w when Mongodb receives too many commands and the database is locked and cannot be executed, it will queue the commands. This column shows the total length of three queues, read and write, and a value of 0 indicates that the mongo is under no pressure. When there is high concurrency, the general queue value will rise.

Current number of connections to conn

Time timestamp

These are the details of the running status parameters of mongodb. Have you gained anything after reading them? If you want to know more about it, you are welcome to follow the industry information!