Before you can hack away at things to speed up your computer, you should know how to monitor system performance in the first place. As a power user, you'll like knowing what's causing those slow-downs and blips in performance. The Performance Console is a great hacker's tool for monitoring and tracking resources of all kinds. Computers get faster every year, but somehow we still end up sometimes waiting around for them to finish a task.
Reducing Visual Effects
Windows XP's visual effects—such as fading and sliding menus, background images for folders, and drop shadows for icon labels—make it the snazziest-looking operating system that Microsoft has yet produced. But all those effects can take their toll on system performance, especially if you have an older computer.
XP gives you the option of balancing these visual effects against system performance. You can go full-bore and use all the visual effects, you can turn them all off, you can have your system decide which to use, or you can pick and choose which effects to turn on and off. Right-click on My Computer and choose Properties > Advanced > Settings (under the Performance section). To turn off all effects, choose "Adjust for best performance." To use all visual effects, choose "Adjust for best appearance." To turn on and off individual effects, choose Custom, then check the effects you want to use and uncheck the ones you don't. Experiment to see how they affect system performance.
To figure out what's slowing your computer down and get to the root of the problem, use the Performance Console (perfmon) to track and graph the activities of Windows XP and its components. First, I'll show you how to set up a log, and then I'll give you some ways to put the console logs to good use.
Setting Up Your Logs
Choose Start > Run and type perfmon. You'll see the Microsoft Management Console (MMC), with the Performance titlebar. In the left pane, click System Monitor to see a graph of your current system performance, including your processor, memory, and disk. You can use the toolbar buttons to configure the graph data and format. This graph is useful for seeing what's going on now, but it's useless for looking at the long-term picture.
To create log files of your system's performance, click Performance Logs and Alerts in the left pane of the MMC. You can create counter logs (with the values of performance indicators, measured on a regular basis), trace logs (with the values of performance indicators when something happens, such as a program crash), and alerts (an action for Windows to take when a counter hits a specified value). Log files stored in text format contain one line per observation, with values separated by either commas or tabs, and are usually stored in the C:\Perflogs folder. You can import these log files into a spreadsheet or database for analysis, reporting, and graphing. SQL and binary (nontext) log file formats are also available. (See article Q296222 in the Microsoft KnowledgeBase for how to log data directly to an SQL database.)
Create a counter log by right-clicking Counter Logs in the left pane and choosing New Log Settings from the shortcut menu. Specify the statistics you want to log by clicking Add Counters on the General tab of the Properties sheet for the log. A nice feature of this utility is that you can choose whether to monitor the local computer or another computer on your LAN. Don't add more than a few counters, or your log file will grow quickly and be confusing to analyze. To select a counter, first select the performance object (i.e., the part of the computer system you want to monitor, such as memory or disks), and then choose counters from the list.
What to watch
These counters are often worth logging:
- \Memory\Pages\sec
-
Number of pages read from disk or written to disk when Windows runs out of memory. Swapping information to and from the disk can slow down your system significantly. Consider adding more memory.
- PhysicalDisk\Avg. Disk Queue Length
-
Number of read and write requests are waiting for the disk to respond. High numbers indicate that a faster disk drive would speed up performance.
- PhysicalDisk\% Disk Time
-
Percentage of the time the disk was busy. This is another indicator of a slow or overloaded disk.
- Processor\% Processor Time
-
Percentage of the time the processor was busy with all types of processes. This counter can tell you whether delays are caused by an overloaded CPU.