Window 7

Performance Testing Guide for Windows

August 18, 2009

Abstract

This paper provides information about testing performance on Windows® 7. It provides guidelines for hardware and software industry professionals, information technology (IT) professionals, and technical users who run performance tests to ensure accurate, repeatable results.

This information applies to the following operating systems:

Windows 7

Windows Vista®

References and resources discussed here are listed at the end of this paper.

The current version of this paper is maintained on the Web at:

http://www.microsoft.com/whdc/system/sysperf/Win7Perf.mspx

Disclaimer: This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein.

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred.

© 2009 Microsoft Corporation. All rights reserved.

Microsoft, MSDN, SuperFetch, Windows, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Document History

Date Change

August 18, 2009 Updated for Windows 7. Includes changes for new Windows features, more detailed methodology, and reorganization.

July 2007 First publication as “Measuring Performance in Windows Vista”

Contents

Introduction 4

Windows Performance Testing Challenges 4

Background Tasks 5

Scheduled Tasks 5

Memory Management and SuperFetch 6

Performance versus Power 7

Performance Test Design Considerations 8

Automating User Presence 8

Testing End-User Scenarios 9

Effects of Hardware on Performance 9

CPU 10

RAM 10

Type of Storage Device 10

Graphics Subsystem 10

Recommended Test Methodology 11

Step 1. Set Up the Operating System 11

Step 2. Set Up the Test Software 11

Step 3. Run Windows Update 11

Step 4. Reboot the System 12

Step 5. Download Windows Defender Definition Files 12

Step 6. Disable Windows Update 12

Step 7. Calculate the Windows Experience Index 12

Step 8. Reboot the System 12

Step 9. Let Windows Defender Build a System File Cache 13

Step 10. Disable User Account Control 13

Step 11. Complete Indexing 13

Step 12. Use SuperFetch to Train the System 14

Step 13. Complete Idle-Time Tasks 15

Step 14. Disable System Restore 15

Step 15. Review Scheduled Tasks 16

Step 16. Run the Test 16

Best Practices 16

Best Practices for Designing Performance Tests 16

Best Practices for Running Performance Tests 17

Resources 17

Appendix. Scheduled Tasks 19

Introduction

A key goal for Windows® 7 is to improve performance in common customer scenarios. To increase system responsiveness and performance, Windows 7 adapts over time to user behavior and takes advantage of the machine’s idle cycles to perform background tasks. Although Microsoft focused on making “in-box” background tasks efficient, these tasks can nevertheless create challenges for those who want to test performance in a controlled environment.

When you evaluate performance, ensure that you understand whether the tests measure raw hardware performance or operating system performance. Tests that measure raw hardware performance often do not represent the types of end-user scenarios for which Windows is optimized. To measure performance in end-user scenarios, use tests that are designed to perform the same kinds of tasks that end users frequently perform.

This paper provides general guidance and points to consider when you conduct performance testing. In particular, it explains how the system adjusts its behavior and how the system services and settings affect performance measurements. By understanding these details, you can ensure consistent results and address issues during testing.

Except as noted, the topics in this paper apply to both Windows 7 and Windows Vista® and the best practices apply to both operating systems.

This paper is intended for hardware and software industry professionals, information technology (IT) professionals, and enthusiasts who want to understand how to measure performance on Windows 7 and Windows Vista.

Windows Performance Testing Challenges

Evaluating Windows performance can be difficult because the operating system attempts to improve its performance over time based on observed usage patterns. The following Windows features present challenges that affect performance evaluation:

• Background tasks.

Some tasks run in the background when the system is idle. Consequently, system behavior changes based on whether the system is idle or a user is interacting with the PC.

• Scheduled tasks.

Scheduled

...