Just as Microsoft has intended it to be the Windows 7 blog run by two key figures of the Windows 7 development team has become one of the central information for information about the upcoming Microsoft operating system. The regular posts give insight into the development process, the development team and decision process but fail to deliver new information about the operating system itself.

It could be seen as a clever ploy by Microsoft to keep the news hungry blogosphere and crowd at bay by taking control of the Windows 7 news flow. Today’s post over at the blog is entitled Windows 7 Approach to System Performance, a much smaller article than the previous ones. Steven Sinofsky is again explaining theoretical and practical concepts that played a role in the Windows 7 development without mentioning any system requirements of the upcoming Windows 7 system.

It is nevertheless a good read from an engineering standpoint. He lists some of the metrics that the Windows 7 team is tracking during development including memory usage, cpu utilization and boot / shutdown / resume / standby times. He mentions criteria that they apply at the end of the milestones before they go into beta which have to be met and that they won’t ship the product if those criteria are not met.

We have criteria that we apply at the end of our milestones and before we go to beta and we won’t ship without broadly meeting these criteria. Sometimes these criteria are micro-benchmarks (page faults, processor utilization, working set, gamer frame rates) and other times they are more scenario based and measure time to complete a task (clock time, mouse clicks). We do these measurements on a variety of hardware platforms (32-bit or 64-bit; 1, 2, 4GB of RAM; 5400 to 7200 RPM or solid-state disks; a variety of processors, etc.) Because of the inherent tradeoffs in some architectural approaches, we often introduce conditional code that depends on the type of hardware on which Windows is running.

He also mentions that some users, usually the technical inclined prefer choice and customization, that some users want more eye candy while others prefer to go back to a Windows 2000 like experience.

..there are limits to what we can provide and at the same time provide a reliable “platform” that customers and developers can count on and is robust and manageable for a broad set of customers. But of course within a known context (within your home or within a business running a known set of software) it will always be possible to take advantage of the customization and management tools Windows has to offer to tune the experience

In conclusion Steven manages to provide some insight into yet another area of development while at the same time failing to provide any factual information about Windows 7.

Subscribe To RSS Feed Updates (What is RSS??)

Bookmark & Share

Related Posts

• Windows 7 Boot Performance
• Engineering Windows 7 Blog Finally Starting To Mention Windows 7
• Windows 7 Development Team
• Will Windows 7 Be A Major Or Minor Release?
• Engineering Windows 7
• Native Support for Virtual Hard Disks in Windows 7
• Microsoft Internal Memo ties Windows Live to Windows 7