Home > database >  Directing a slow query
Directing a slow query

Time:09-17




Fri Oct 25 00:34:03. 451 I COMMAND [conn645853] COMMAND app_test. SmashEgg COMMAND: getMore {getMore: 301616208827, the collection: "SmashEgg} planSummary: IXSCAN {1} _id: cursorid: 301616208827 keysExamined: 390541 docsExamined: 390541 cursorExhausted: 1 keyUpdates: 0 writeConflicts: 0 numYields: 3059 nreturned: 213 reslen: 62830 the locks: {Global: {acquireCount: {r: 6120}}, the Database: {acquireCount: {r: 3060}}, collection: {acquireCount: {r: 3060}}} protocol: op_command 960 ms



Online mongo database often appear such circumstance, good solution to solve the great god?

Ps: the building of index have, every time the execution of the query number is controlled, but there is no effect,

CodePudding user response:

IXSCAN {_id: 1}
Index - look for and provide specific statement

CodePudding user response:

Walk is index, the specific statement execution is not, to run code development, directing and since you are buying online, only the slow query log, what other log all have no, so fidgety
  • Related