

- "Basic XP" refers to the standard install, without Office 2007, so there are only 710 files to be tested.
- "WDD" refers to the read times of the same 802 files, after several defrag passes using the WDD Defrag button. A 26% performance improvement is measured. You could expect this result on a "clean" install machine.
- "Basic Office" refers to the read time of all 802 test files, where no defragmentation has been done whatsoever, before or after the installation of Microsoft Office 2007 Professional.
- "Full WDD" refers to the read time of all 802 test files after several reboots and several passes using the WDD defrag button. A 28% performance improvement has been measured.
- "Auto" is an interesting result. The system was left without any defragmentation, but rebooted once or twice a day for 6 days. This was done by changing the date on the laptop, and allowing several hours between each reboot.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft
\Windows\CurrentVersion\OptimalLayout]
"EnableAutoLayout"=1
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft
\Dfrg\BootOptimizeFunction]
"Enable"="Y"
Conclusion: WDD can reduce program load times by around 27% compared to a badly maintained system. Scheduling a regular defrag (once a month for low-usage systems) will help prevent the system from experiencing major slowdowns caused by file fragmentation. if your system starts getting sluggish, try running WDD's Defrag manually. Also use a program like CCleaner to clean out junk from your system. Another useful option is the undocumented "defrag c: -b" command, which is supposed to do the boot optimize on demand.
2 comments:
Before benchmarking, you should also boot to Safe Mode (command prompt) and run defrag (assuming drive C: for Windows) as follows:
defrag c -b
This is a hidden switch for the Windows XP defragger that will force a rearrangement of the critical system files based on the layout.ini file in order to speed up boot time.
Thanks for the info! This is most useful.
I used the command
rundll32.exe advapi32.dll,ProcessIdleTasks
which hopefully after 3 reboots will have achieved the same effect. I also moved the date forward by 4 days before the final reboot in order to force the "regular" defrag.
I will experiment with the -b option and see if it affects the results in any substantial way.
Post a Comment