[SERVER-16305] Suppress saveState , restoreState stats from profiling output for WT Created: 24/Nov/14  Updated: 24/Jan/15  Resolved: 23/Jan/15

Status: Closed
Project: Core Server
Component/s: Diagnostics, Storage
Affects Version/s: 2.8.0-rc1
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Jalpa Trivedi (Inactive) Assignee: David Storch
Resolution: Done Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-16020 Suppress non-applicable profiling dat... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

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 .



 Comments   
Comment by David Storch [ 23/Jan/15 ]

Since this ticket was filed, yielding has been enabled for servers configured with the WiredTiger storage engine. Therefore, the saveState and restoreState metrics are useful regardless of storage engine. Closing this ticket accordingly as Works as Designed.

Comment by Andy Schwerin [ 24/Nov/14 ]

As there is modest chance that the yielding concept will be introduced in the WT engine for 2.8, I think we should consider saveState and restoreState applicable for the time being. The most I would do is suppress outputting those fields when they have a value of 0.

Generated at Thu Feb 08 03:40:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.