{"id":5117,"date":"2020-10-28T15:59:26","date_gmt":"2020-10-28T22:59:26","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/pix\/?page_id=5117"},"modified":"2021-09-14T17:29:10","modified_gmt":"2021-09-15T00:29:10","slug":"analyzing-win32-file-io-performance-in-timing-captures","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/pix\/analyzing-win32-file-io-performance-in-timing-captures\/","title":{"rendered":"Analyzing Win32 File IO performance in Timing Captures"},"content":{"rendered":"
\n

PIX Timing Captures<\/a> include an option to collect data on your title\u2019s use of the Win32 file IO APIs to access files. The data collected for calls to APIs such as ReadFile and WriteFile include the name of the file being accessed, and the offset, size and duration of the access itself. Full callstacks for each file access are also recorded.\u00a0 If your title packages individual assets into a composite archive file, PIX can show which assets within the composite file were accessed if a mapping file is provided.<\/p>\n

When file IO data is collected, PIX also computes drive bandwidth and utilization metrics. File IO data is displayed in the Timeline<\/strong>, Range Details<\/strong>, Element Details, <\/strong>and Metrics<\/strong> views in Timing Captures.<\/p>\n

Capturing Win32 File IO data<\/h3>\n

To capture data on Win32 file accesses, select the File accesses<\/strong> check box when starting a Timing Capture as shown in the following figure.<\/p>\n

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

\n
\n

Analyzing Win32 File IO accesses in the Timeline<\/h3>\n

PIX creates an IO lane in the Timeline<\/strong> for each drive on the PC from which files were read. Individual file access are represented by a colored rectangle that contains the name of the file that was accessed. The start of each rectangle and it\u2019s length represent the start time and duration of the access. Details of each access are provided in a tooltip.<\/p>\n

The following picture shows several reads of a file named ExampleFileData.dat on the E: drive. Note that several rectangles indicating accesses of ExampleFileData.dat overlap in time and are stacked on top of each other in the lane. This visualization represents several concurrent reads of the file.<\/p>\n

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

To view Win32 File IO data in a tabular form, select a range of time in the Timeline<\/strong> and choose the File IO Events<\/strong> item from the Items to Show<\/strong> dropdown in the Range Details<\/strong> view. Viewing timing data in a table is useful for certain scenarios such as sorting the table by the file accesses that took the longest time to complete.<\/p>\n

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

Selecting a row in Range Details<\/strong> populates the Element Details<\/strong> view with more detailed data about the file access, including the callstack in your title that initiated the access. Use the Show in Timeline<\/strong> button to scroll the Timeline<\/strong> to the point in time when the access occurred.<\/p>\n

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

<\/h3>\n

Analyzing file accesses that occur within archive files<\/h4>\n

By default, PIX shows file accesses as seen by the underlying file system. If your title packages individual assets into a composite archive file, the file io profiler built into Timing Captures can now show which assets within the composite file were accessed, but it requires extra information from you, the title developer, to do so.\u00a0 The extra information you supply is in the form of a Mapping File that PIX uses to decode accesses that occur within archive files.\u00a0 A mapping file consists of a list of entries, where each entry specifies the size of a specific asset, along with its offset from the beginning of the archive file.\u00a0 A description for each asset must also be provided. PIX uses this offset and size information to map accesses that occurred within the archive to the specific asset, or set of assets, that was read.\u00a0 It then uses the description supplied for each asset to identify it in various places in the Timeline<\/strong>, Range Details<\/strong>, and Element Details<\/strong> views.<\/p>\n

Mapping File Format<\/h5>\n

Mapping files are in .csv format. The format should be easily producible either manually or from the portion of your build system that composes the archives.<\/p>\n

The first line of the mapping file must be the file name of the archive file that the entries in the rest of the mapping file apply to.<\/p>\n

Example first line:<\/p>\n

c:\\MockGame_PC\\assets\\armor_assets.packed<\/p>\n

The remaining lines in the mapping file identify the individual assets within the archive. Assets are identified by the byte offset within the archive file where the asset is stored, the size of the asset in bytes and a description of the asset. The format of an asset line is<\/p>\n

<offset>,<size>,<description><\/p>\n

Example asset line:<\/p>\n

0x000000000001FA0, 8096, armor\\body\\helmet.s<\/p>\n

The offset and size values on an asset line can be specified as either hex or decimal numbers.<\/p>\n

Mapping files may also contain lines that are comments. PIX will ignore these lines when processing the mapping file. Comments lines start with a #.<\/p>\n

Example comment line:<\/p>\n

# this line is a comment. Ignored by PIX.<\/p>\n

An example of a complete mapping file follows:<\/p>\n

armor_assets.packed<\/p>\n

0x000000000000000, 8096, armor\\weapons\\sword.s<\/p>\n

0x000000000001FA0, 8096, armor\\body\\helmet.s<\/p>\n

0x000000000003F40, 8096, armor\\weapons\\sabre.s<\/p>\n

# this line is a comment, ignored by PIX<\/p>\n

0x000000000005EE0, 8096, armor\\body\\mail.s<\/p>\n

0x000000000007E80, 8096, armor\\body\\gloveR.s<\/p>\n

0x000000000009E20, 8096, armor\\weapons\\chain.s<\/p>\n

 <\/p>\n

Working with Mapping Files<\/h5>\n

The Display Options<\/strong> panel in the Range Details<\/strong> view includes an Add Mapping Files…<\/strong> button when File IO Events<\/strong> is selected from the Items to Show<\/strong> dropdown.\u00a0 Clicking Add Mapping Files…<\/strong> brings up a dialog you can use to select your mapping files(s).<\/p>\n

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

After processing the mapping file(s), PIX displays a dialog indicating whether any warnings or errors were encountered.\u00a0 A description of each warning and error is contained in the Output<\/strong> view.\u00a0 Note that malformed lines in a mapping file are considered warnings, not error.\u00a0 PIX will skip any malformed lines and continue processing the mapping file.\u00a0 The following picture shows the status dialog and contents of the Output view when errors and warnings are found.<\/p>\n

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

The UI is updated with the asset names for each line in the mapping file in which the offset and size match a file access that occurred when the capture was running.\u00a0 The Range Details<\/strong>, Element Details<\/strong>, and Timeline<\/strong> views are all updated with asset names.<\/p>\n

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

 <\/p>\n

Drive Bandwidth and Utilization Metrics<\/h3>\n

When file io data is collected, PIX computes drive utilization and bandwidth counters for each drive on your PC.\u00a0 These counters can be found under the Derived System Metrics\/Drive Utilization<\/strong> node in the Metrics View Selector Panel.<\/p>\n

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

The integration between views in PIX makes it easy to draw correlations between the disk metrics and the data on individual reads.\u00a0 The following picture shows a custom layout comprised of a Metrics<\/strong> view, a Range Details<\/strong> view, and an Element Details<\/strong> view.\u00a0 The Range Details<\/strong> view is configured to display data corresponding to the selected time range in the Metrics<\/strong> view.<\/p>\n

A period of time is selected in the Metrics view that corresponds to spikes in drive utilization and bandwidth.\u00a0 Selecting File IO Events<\/strong>\u00a0from the\u00a0Items to Show<\/strong>\u00a0dropdown in Range Details<\/strong>, populates the table with the set of file accesses made by the title during that period of time.\u00a0 Selecting an individual access populates the Element Details<\/strong> view with details about that access, including the callstack of title code that initiated the access.<\/p>\n

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

Win32 File IO Lane Configurations<\/h3>\n

The Lane Selector panel and the Lane Configurations list box can be used to customize the appearance of IO lanes as shown in the following picture. Options to reorder lanes, to display or hide specific lanes, to adjust the color and marker height, and other options are provided.<\/p>\n

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

PIX Timing Captures include an option to collect data on your title\u2019s use of the Win32 file IO APIs to access files. The data collected for calls to APIs such as ReadFile and WriteFile include the name of the file being accessed, and the offset, size and duration of the access itself. Full callstacks for […]<\/p>\n","protected":false},"author":1915,"featured_media":4769,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5117","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pix"],"acf":[],"blog_post_summary":"

PIX Timing Captures include an option to collect data on your title\u2019s use of the Win32 file IO APIs to access files. The data collected for calls to APIs such as ReadFile and WriteFile include the name of the file being accessed, and the offset, size and duration of the access itself. Full callstacks for […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/posts\/5117","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=5117"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/posts\/5117\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/media\/4769"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/media?parent=5117"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/categories?post=5117"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/tags?post=5117"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}