5/15/2023 0 Comments Iograph windowsDue to a large number of applications and services starting up during system boot, the boot IO patterns can vary from run to run, especially in the later phases of boot where more activity occurs in parallel.6,283,264 bytes are then satisfied from the ReadyBoot RAM cache while 391,168 bytes are serviced from the hard drive. In the example above, lsass.exe requests a total of 6,674,432 from the disk.To see the total read footprint of an application, one should look at the totals of ReadyBoot hit and miss events. Pend event always overlaps with either a hit or miss event. Note that some of the reads from lsass.exe hit in the ReadyBoot cache (hit events), while some missed the cache and went down to the hard drive (miss events).Īlso note that pend event type category shows read request that were held up by ReadyBoot before turning into hits or misses. The following screen shot shows a ReadyBoot Event table displaying lsass.exe ReadyBoot activity.Įxpanding the process of interest, in this example lsass.exe, observe the kinds of IO that process has been doing during the selected interval. Rearrange the column in the summary table (by dragging the column headers) to have "Process" on the very left, followed by the "Event Type", followed by "Path Name". This can be an interval the application in question was running or the entire boot interval. Select the interval of interest on the ReadyBoot I/O graph. ReadyBoot Events Table provides the necessary IO information. Recall that Disk IO graph and Summary Tables do not reflect the read requests which hit the ReadyBoot RAM cache. This example demonstrates how to determine how much disk IO a given application is doing during boot and what files it is accessing. In this article Example 1: Understanding Your Application's Boot Read Footprint
0 Comments
Leave a Reply. |