Get maximum performance from Windows Vista
Windows Vista includes a number of tools that you can use to pinpoint performance bottlenecks. Some of these, such as the System Health Report, the Windows Experience Index, and the Reliability Monitor, provide static snapshots showing the resources available to your system and where those resources might not be adequate to your needs. Others, such as the venerable Windows Task Manager, the new Resource Overview, and Performance Monitor (an improved version of the tool known in Windows XP as System Monitor), let you track a variety of performance metrics in real time.
In addition to these snapshot and monitoring utilities, Windows Vista incorporates the following forms of performance-enhancing technology: SuperFetch, ReadyBoost, ReadyDrive
All three of these are designed to reduce the amount of time your system spends engaged in performance degrading disk IO. SuperFetch is a memory management technology that observes your computer usage patterns over extended stretches of time (noting the programs you run and the days and times you typically run them) and adjusts caching behavior to accommodate your own particularities. ReadyBoost uses external memory devices (such as USB 2.0 flash disks) to cache disk content of all kinds, reducing the need for time consuming hard disk access. And ReadyDrive is technology that supports the use of hybrid hard disk drives drives that incorporate nonvolatile flash memory (NVRAM) as well as conventional rotating disk media. Hybrid drives are particularly useful for extending battery life on portable computers, because they reduce the need for drive spin.
SuperFetch is useful to anyone running Windows Vista. You don’t need to do anything except be glad that it’s there. ReadyDrive should be of interest if you’re in the market for a new computer and hybrid drives are a purchase option. ReadyBoost, in contrast, is of no value unless you implement it by attaching a suitable external memory device to your system. For details, see “Using ReadyBoost” later in this article.
This tips will review these basic performance enhancing strategies:
- Ensuring that you have adequate RAM
- Ensuring that you have an adequate virtual memory configuration
- Using ReadyBoost
- Managing startup programs
- Keeping your disks defragmented
- Maintaining adequate free space on your disks
- Avoiding tweaks of dubious value
Ensuring that you have adequate RAM
Random access memory (RAM) is the vital stuff that keeps Windows running smoothly. Having enough physical (main) memory helps reduce the operating system’s dependence on virtual memory, thereby minimizing the number of number of times Windows has to swap information between fast memory chips and your (relatively slow) hard disk. How much memory do you need?
The “Windows Vista Capable” and “Windows Vista Premium Ready” stickers that appear on some new hardware are based on standards expressed at the Windows Vista Enterprise Hardware Planning Guidance site. According to these standards, a system needs 512 MB to be “Windows Vista Capable” and at least 1 GB to be “Windows Vista Premium Ready.” You should consider “Windows Vista Capable” to mean adequate (if barely) for Windows Vista Home Basic. For the more feature rich editions of Windows Vista Home Premium, Business, and Ultimate treat the “Windows Vista Premium Ready” standards as a minimum. In any case, doubling these minimums will provide a better ride for most users.
You can gauge the adequacy of your computer’s physical memory by watching the Memory graph in the Resource Overview section of the Reliability and Performance Monitor (to open this tool, click the Start buttonPicture of the Start button , type perfmon, and then press ENTER). The blue line on the graph indicates the percentage of your physical memory that’s currently in use. If this line hovers in the sub arctic zone (say, north of 60 percent) most of the time under your typical working conditions, you might want to consider adding memory to your computer, particularly if you are also seeing the green line on the same graph, the line that indicates the number of hard faults per second your system is generating, spike off the top of the graph for extended periods of time. (A hard fault, which despite its name is not an error condition, is an instance where a block of memory needed by the operating system has to be fetched from the page file on the hard disk. A high number of hard faults per second indicates a large perhaps excessive reliance on virtual memory, with consequent adverse performance effects.)
Ensuring that you have an adequate virtual-memory configuration
Physical memory might be the vital lubricant of a happily humming Windows machine, but Windows is not designed to run on RAM chips alone, no matter how many of them you have. In addition to using physical RAM to store programs and data, Windows creates a hidden file on your primary hard disk and uses that file to swap pages of data out of physical memory when necessary. The “swap file” (these days more commonly called a page file) acts as an extension of main memory or, in other words, as virtual memory.
In a default installation, Windows creates the page file in the root folder on the same drive that holds the Windows system files. The size of the page file is determined by the amount of RAM in your system. By default, the minimum size is 1.5 times the amount of physical RAM, and the maximum size is three times the amount of RAM (twice the minimum). You can see the page file in a Windows Explorer window if you configure Windows to show hidden and system files; look for Pagefile.sys in the root of your system drive.
To see the current configuration of your system’s virtual memory, click the Start button, click Control Panel, click System and Maintenance, click Performance Information and Tools, click Advanced Tools (in the Tasks pane at the left side of the dialog box), and then click Adjust the appearance and performance of Windows. After answering the User Account Control prompt, you’ll arrive at the Performance Options dialog box. You’re nearly there; click the Advanced tab, and then click Change. The image below shows the Virtual Memory dialog box, with default settings for a machine with 2 GB of RAM (default, that is, except that we cleared the Automatically manage paging file size for all drives check box to make the rest of the dialog box easier to read).
By default, Windows creates a single page file in the root folder on the same volume that holds the Windows system files and manages its size for you. The Currently allocated number near the bottom of the dialog box shows you how large the file is now. If conditions on your system change (you run an unusually large assortment of memory-intensive applications, for example), Windows might expand the page file. It might then return the file to its original size (or a smaller size) if the demand subsides. All this happens without intervention or notification if you leave the Automatically manage paging file size for all drives check box selected.
If you don’t want Windows to do this for you, you have the following options:
- You can move the page file to a different volume, if you have more than one.
- If you have more than one volume, you can establish more than one page file.
- For any page file, you can choose between System managed size and Custom size.
- If you choose Custom size, you can specify an initial size and a maximum size.
You can remove a paging file from a volume by selecting the volume and choosing No paging file. (You can even get rid of all paging files this way, although doing so is not recommended, even on systems with a lot of RAM.)
Should you get involved in page-file management, and, if so, how?
If you have more than one physical disk, moving the page file to a fast drive that doesn’t contain your Windows system files is a good idea. Using multiple page files split over two or more physical disks is an even better idea, because your disk controller can process multiple requests to read or write data concurrently. Don’t make the mistake of creating two or more page files using multiple volumes on a single physical disk, however. If you have a single hard disk that contains C, D, and E volumes, for example, and you split the page file over two or more of these, you might actually make your computer run more slowly than before. In that configuration, the heads on the physical disk have to do more work, loading pages from different portions of the same disk sequentially, rather than loading data from a single contiguous region of the hard disk.
If you are short of hard disk space, you might consider setting a smaller initial page file size. You can use a handy script from Windows MVP Bill James to monitor current page file usage and session peak usage. This tool, a free download at BillsWay.com, was written for Windows XP but works fine in Windows Vista. If this script nearly always shows current and peak usage levels well below the current page file size, you might want to consider reducing the initial size to save disk space. On the other hand, if you’re not short of disk space, there’s nothing to be gained from doing this and you might occasionally overload your custom settings, thereby degrading the performance of your system.
Should you enlarge your page file? Most users won’t need to do this. But you might want to keep an eye on the green line in the Memory graph of Resource Overview, as described above in “Ensuring that you have adequate RAM.” If that line is spiking off the top of the graph a great deal of the time during your normal work, you might consider increasing the maximum size of your page file. (Disregard page file spikes and disk activity in general that takes place while you’re not actually working. This is likely to be the result of search indexing, defragmentation, or other background processes and does not indicate a problem with your actual work performance.)
NoteFor more information about page file management in Windows, we recommend the article “Virtual Memory in Windows XP” on the Windows Support Center website. Although the file magnitudes discussed in this article are pertinent to the Windows XP environment rather than to Windows Vista, the basic information about how Windows manages and uses page files is still useful and valid.
Share and Enjoy:
Tags:configuration, flash memory, hard disk, Management, memory, pagefile, Performance, performance monitor, physical ram, Prompt, readyboost, ReadyDrive, ROOT, SuperFetch, system, System Health Report, Tip, Virtual, virtual memory, Windows, windows system, windows task manager, windows vista
Related posts
- Save space when using two drives or dual-booting (0)
- Sizing up your boot drive’s pagefile (0)
- How to Disable SuperFetch on Windows Vista (0)
- Increasing the Speed of a Vista-Operated PC (4)
- How to Perform Disk Defragment Windows Vista from the Command Line (0)
- Freeup Memory In One Click With Instant Memory Cleaner (0)
- Bootup Faster from Windows Vista (0)
- Windows XP and Vista: The Benchmark Rundown (1)
- Vista SP1 Evolves Performance Boost (0)
- Vista Free Downloads to Tweak & Improve Your System (4)
- Top Ten Tips to Speed Up Windows Vista (1)
- Top 10 Causes your computer slows (1)
- Tips for a well-behaved PC (1)
- Origami Experience 2.0 for Windows Vista (0)
- Optimize Windows Vista for better performance (1)
- Improve performance by tweaking your hardware (0)
- Hardware Restrictions In Vista (0)
- Free Download Windows Vista - Sysinternals Suite (2)
- Easily Transfer Your Old Files to a New Vista PC (0)
- Delete files using Disk Cleanup (0)
- Boost your performance with ReadyBoost (1)
- XP virtual computing avoids dual-boot complexity (0)
- Windows Vista VHD (Virtual Hard Disk for Virtual PC) (0)
- Windows Vista SP1 Security Vulnerabilities (0)
- Windows Vista SP1 Improves Speed Up to 86% Faster (4)
Written by Jason on August 24th, 2008 with no comments.
Read more articles on 1340 and 1354 and 1426 and 1429 and 1673 and 169 and 2065 and 2157 and 401 and 544 and Contributors and Performance and Prompt and ReadyBoost and ReadyDrive and System Health Report and Virtual and Windows Vista and configuration and hard disk and management and memory and pagefile and physical ram and system and tip and virtual memory and windows and windows system and windows task manager.
