Remarks on Windows Disk and File IO During System Boot

Let use take a look at some graphs I created with Windows Performance Analyzer (WPA), showing a typical corporate laptop boot Windows 7. Detailed information on creating such a trace can be found in my earlier article Analyzing a Slow Boot with Windows Performance Recorder & Analyzer.

Disk and File IO during Windows 7 boot - Windows Performance Analyzer

Analysis

Several things can be learned analyzing the graphs:

  • IO count and IOPS are much higher when measured at application level (top graph) versus at disk level (bottom graph) - notice the different scaling of the y-axis! See my earlier article The Impossibility of Measuring IOPS (Correctly) for more information on this topic.
  • Contrary to popular belief the boot phase IO pattern shows not only reads, but a substantial amount of writes, too: 16% in this case. I am sorry about the colors, by the way. I tried but could not get WPA to change the colors so that reads and writes look less similar.
  • Windows’ boot phase obviously is very IO intensive. In this case we have a total of 62,000 IOs over a time period of 330 seconds which amounts to 188 IOPS on average. That is not bad for a poor magnetic hard drive at all, but this system would benefit greatly from an SSD.

Bonus takeaway: IOPS are a function not only of the drive speed but also of the application(s) generating the IOs.

Comments

Related Posts

Performance Impact of Windows Offline Files

A little known fact about the Windows Offline Files functionality is it slows down network operations considerably. Here is how and why. Test Results The following tests were performed with a set of 1,114 files of a total size of 408 MB. In the copy test the files were copied from a Windows 7 client machine to a file server over a 100 MBit LAN connection. In the delete test the files were deleted on the file server. No antivirus or other security products were running on either side. Each test was run twice, the table lists the average.
Networking

Boot IO Analysis with uberAgent for Splunk 1.5

Boot IO Analysis with uberAgent for Splunk 1.5
Analyzing slow boots is a difficult task. You need to install software like XPerf and master its far-from-intuitive command-line options to generate a trace file that you can then analyze. Once you find a possible cause for the long startup duration you never know if it is specific to the machine you analyzed or if it affects other PCs, too. In other words: XPerf, although powerful, is difficult to master. And it does not scale. uberAgent does. And it is super-easy to use.
Logs & Metrics

Latest Posts