{"id":5713,"date":"2022-01-04T16:43:09","date_gmt":"2022-01-05T00:43:09","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/pix\/?p=5713"},"modified":"2022-01-25T13:39:34","modified_gmt":"2022-01-25T21:39:34","slug":"graphing-consolidated-events-in-the-timing-capture-metrics-view","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/pix\/graphing-consolidated-events-in-the-timing-capture-metrics-view\/","title":{"rendered":"Graphing Consolidated Events in the Timing Capture Metrics View"},"content":{"rendered":"

The 2201.24 release of PIX on Windows<\/a> includes a feature that treats a set of events that follow a common naming pattern as the same event in the Timing Capture<\/a> Metrics view.\u00a0 You’ll find this feature useful if you follow the common practice of naming the PIX events that represent a frame of CPU work (or any other repeated set of work) with a sequential number pattern, as in this example:<\/p>\n

\"Image<\/a><\/p>\n

\n
\n

In this case, using the Metrics View to analyze an individual frame event, such as “Frame 339” isn\u2019t useful, but analyzing the set of “Frame *” events as a group can be used to find outliers in frame time.<\/p>\n

When populating the Selector<\/em> panel, PIX will look for events whose names follow a particular pattern.\u00a0 These events are then grouped, or consolidated. The individual events that fit the patterns will be treated as the same event for purposes of graphing and analysis.<\/p>\n

Events that start with the same string, followed by one or more spaces, followed by a number will be consolidated. For example, from the picture above, the events \u201cFrame 334\u201d, \u201cFrame 335\u201d, \u201cFrame 336\u201d and so on, will be consolidated and graphed as a single event in the Metrics view.<\/p>\n

The number at the end of the pattern may be either an integer or a decimal number. If the number is a decimal, it must have values on both sides of the decimal point. For example, the events \u201cRender 10.987\u201d and \u201cRender 12.789\u201d would be consolidated.<\/p>\n

The consolidated events are shown in a separate node in the Selector<\/em> panel tree under PIX CPU Events<\/strong>, as shown in the following figure.<\/p>\n

\"Image<\/a><\/p>\n

\n
\n

Note that events are only consolidated for PIX CPU events. PIX GPU events do not currently support consolidation.<\/p>\n

Clicking the checkbox next to a consolidated event will add the group of events to the Active Metrics<\/em> panel just as with a standard event. Hovering over a point in the graph will show the name of the underlying event, as shown in the following figure.<\/p>\n

\"Image<\/a><\/p>\n

\n
\n

The consolidating of events also occurs when the Metrics View<\/em> is navigated to from the Timeline View. In the following picture, graphing the event MainLoop 7769<\/strong>, which matches the consolidation pattern, will cause the consolidated event MainLoop *<\/strong> to be added to the Active Metrics panel.<\/p>\n

\"Image<\/a><\/p>\n

\n
\n

There may be times when the algorithm PIX uses to consolidate events results in the grouping of a set of events that should instead be kept separate. If this occurs, uncheck the Enable Metrics View Consolidated Events (requires re-open of capture)<\/em> checkbox in the Settings<\/em>view.<\/p>\n

\"Image<\/a><\/p>\n

As always, use the PIX feedback button in the upper right corner of the UI to send us feature requests and bug reports.<\/p>\n<\/div>\n

Steven.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

The 2201.24 release of PIX on Windows includes a feature that treats a set of events that follow a common naming pattern as the same event in the Timing Capture Metrics view.\u00a0 You’ll find this feature useful if you follow the common practice of naming the PIX events that represent a frame of CPU work […]<\/p>\n","protected":false},"author":1915,"featured_media":5718,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5713","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pix"],"acf":[],"blog_post_summary":"

The 2201.24 release of PIX on Windows includes a feature that treats a set of events that follow a common naming pattern as the same event in the Timing Capture Metrics view.\u00a0 You’ll find this feature useful if you follow the common practice of naming the PIX events that represent a frame of CPU work […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/posts\/5713","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/users\/1915"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/comments?post=5713"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/posts\/5713\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/media\/5718"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/media?parent=5713"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/categories?post=5713"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/tags?post=5713"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}