-
Type:
Improvement
-
Resolution: Done
-
Priority:
Minor - P4
-
None
-
Affects Version/s: 2.8.0-rc1
-
Component/s: Diagnostics, Storage
-
Fully Compatible
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Example Profiling document for WT:
{
"op" : "query",
"ns" : "test.system.profile",
"query" : {
"op" : "insert"
},
"cursorid" : 14724506024,
"ntoreturn" : 0,
"ntoskip" : 0,
"nscanned" : 0,
"nscannedObjects" : 101,
"keyUpdates" : 0,
"nreturned" : 101,
"responseLength" : 19917,
"millis" : 1,
"execStats" : {
"stage" : "COLLSCAN",
"filter" : {
"op" : {
"$eq" : "insert"
}
},
"nReturned" : 101,
"executionTimeMillisEstimate" : 0,
"works" : 102,
"advanced" : 101,
"needTime" : 1,
"needFetch" : 0,
"saveState" : 0,
"restoreState" : 0,
"isEOF" : 0,
"invalidates" : 0,
"direction" : "forward",
"docsExamined" : 101
},
"ts" : ISODate("2014-11-24T21:54:23.550Z"),
"client" : "127.0.0.1",
"allUsers" : [ ],
"user" : ""
}
Notice that execStats.saveState and execStats.restoreState is 0. It is always 0 for all the documents. It seems to be related to yielding and since numYield was suppressed from WT (SERVER-16020), we should probably suppress execStats.saveState and execStats.restoreState .
- is related to
-
SERVER-16020 Suppress non-applicable profiling data when using WT
-
- Closed
-