Speed searching
Tweaking Windows for rich-media performance.
By Brian Dipert, Technical Editor -- EDN, 10/30/2003
In this age of rich-media applications, even relatively recent PCs can come up short in performance. From audio to photographs to video, digital-consumer applications provide a stiff processing challenge. In addition, PCs simply tend to bog down over time as we install and uninstall programs and perform seemingly countless Microsoft updates.
I recently found myself in this predicament with my Fujitsu Lifebook P2040, which features an 800-MHz Transmeta Crusoe CPU and runs Windows XP Professional. Over time, bloated code and numerous background Windows processes had straightjacketed what was once a nimble-running machine. The sluggish performance I experienced when viewing EDN's new digital version drove me to action.
Not yet ready to replace my PC, I instead experimented with various performance-enhancing adjustments. The results of my testing should benefit anyone who'd like to help an aging PC last a little longer and keep up with today's digital-media applications. If you're not running Windows XP, some of what I discuss will still apply to you.
For many of the steps highlighted below, the sidebar "Roll up your sleeves" provides detailed instructions and expanded explanations. Finally, I make no guarantees, nor do I accept responsibility for any problems that may result from implementing these suggestions. They've worked for me and others, but your mileage may vary, and you should proceed at your own risk.
EXCISE EYE CANDY: Much ado has been made about Windows XP's GUI (graphical user interface). Some people like the new look, but others can't stand it. Personally, right after firing my PC up for the first time, I switched Windows to its "Classic" GUI mode. Regardless of your GUI preference, Windows XP includes a number of animation, fading, translucence, and other visual effects that, if your PC has a trailing-edge graphics subsystem like mine, can hinder its snappiness. Luckily, you can turn them all off.
CUT COLOR DEPTH: I was somewhat reluctant to perform this step, but throttling my graphic chip's color depth back to 16 bits/pixel (instead of 24 or 32) led to a significant boost in performance. More bits per pixel means more traffic running across PCI or AGP to the graphics subsystem, along with more per-pixel processing within the graphics subsystem. My Windows icons don't look quite as nice at 16 bits, but few applications actually benefit from increased color depth.
This move paid off particularly well when watching DVDs. In 24-bit mode, CyberLink PowerDVD dropped a significant number of video frames, leading to a jerky presentation. But playback was silky smooth in 16-bit mode, even with MIPS-gobbling audio features such as Dolby Headphone turned on. Adobe Acrobat and Acrobat-based programs, including the Zinio reader program used with the digital version of EDN, also saw a big performance boost from the color-depth downshift.
DOWNLOAD DRIVERS: Next, I made sure that I was running the latest version of the driver suite for my graphics chip. This practice is also good for other PC subsystems. Checking regularly for updates to audio and core-logic software, for example, can reap big rewards. Intel's Application Accelerator and Via Technologies' 4-in-1 driver suite serve as good examples.
TWEAK WITH TOOLS: TweakUI, a tool you can download from Microsoft's Web site, provided a big return on investment—especially considering that it's free. With the program, you can drastically increase the speed with which menus appear and disappear, adjust mouse-button sensitivity, and make many other performance-related changes. Another utility, Xteq Systems' X-Setup, provides even more adjustment options, but also offers possibilities that can really mess up your system if you don't know what you're doing.
FINAGLE FORMAT: Some folks believe that converting your drive from FAT32 (32-bit file-allocation table) to NTFS (New Technology File System) format will generate a speed boost. Others maintain that the change will result in a slight performance decrease. Regardless, NTFS is the newer, more robust and fuller featured option, so most people recommend the conversion—as long as you don't need to run a Windows ME- or 9x-based configuration, or another operating system, on that same partition.
DO DMA: If (and only if) your hard disk, optical drive, and other peripherals connected to the IDE bus support DMA (Direct Memory Access), ensure that Windows is running them in this mode instead of the much slower PIO (Parallel Input/Output) mode.
In addition, you should periodically check to make sure that the drives remain in DMA mode. If Windows encounters drive errors, such as if you attempt to write to a defective optical disc, it'll permanently throttle back to PIO mode. Fixing this feature requires an operation not for the faint of heart. Uninstall the channel in Device Manager, reboot, and let Windows find it and reinstall its drivers. Don't forget, too, to fix the problem that caused the PIO conversion in the first place.
POLICE PAGING: Many people recommend overriding Windows' management of the virtual-memory paging file (also known as a swap file). I didn't see much of a speed boost from this action, but again, others have.
FERRET OUT FRAGMENTING: At this point, you're likely to have a fragmented paging file that's constructed out of available clusters scattered across your drive. For best performance, defragment the drive to collect the paging file into one contiguous string of clusters. Doing so will also speed up access to all of the files on your system. The defrag utility included with Windows is incomplete in that it doesn't work on system files that are in use, including the paging file. In this case, I'd recommend Executive Software's Diskeeper, which includes a mode in which it runs before Windows boot.
REVISE THE REGISTRY: Now that you've got your drivers and other startup programs organized, turn your attention to the order in which the Windows Registry loads them during system boot. BootVis, another free utility available from Microsoft, monitors your system as Windows loads, then reorganizes the launch order of various pieces of software to remove dependencies and maximize boot speed.
As before with the paging file, I didn't perceive much improvement after running BootVis. In addition, because Hibernate works well and because Windows XP is so much more stable than previous operating systems, I find that I'm not rebooting very often anyway. However, other BootVis users have reported dramatic acceleration, so it's worth a try.
BOOT THE BLOAT: To boost the amount of available hard-drive space, you might want to scale back the default sizes of the Internet Explorer cache, the Recycle Bin, and System Restore. The default settings, based on percentages of the total partition size, have bloated to unnecessary proportions in this era of multigigabyte drives. You should also regularly run Disk Cleanup to clean out your browser cache and eliminate unnecessary, space-consuming files in your temp directories.
To compress the Windows Registry database, which doesn't automatically shrink when you uninstall programs, and to eliminate leftover program references, you might want to try running a registry-cleanup utility. Microsoft's RegClean supposedly doesn't support Windows XP, so I haven't tried it (operating under a "better safe than sorry" policy). However, some folks report success with it. Companies such as Symantec also offer registry-maintenance programs.
BITE THE BULLET: All of the above may prove helpful to you. But beyond a certain point, tweaking meets with diminishing returns. To gain more performance, you'll need to pull out the screwdrivers (and your credit card) and replace some of the PC's hardware. In the end, I upgraded my RAM and switched to a hard-disk drive with a higher RPM rating. The latter change in particular netted a dramatic improvement (see the sidebar "The hard(ware) way").
With all the modifications I've made, I think I can live with this computer for a long while. But, alas, I'm probably only a Microsoft patch away from further frustration.
| Author Information | ||||
|
|















You can reach Technical Editor Brian Dipert at 1-916-454-5242, fax 1-617-558-4470, 