Home > Life > dcomments.blogs.l.lifehacker [ Add to favorite]
|
|
|
|
Blog > newsgroup > comments > blog
|
|
![]() |
Disabling QoS to Free Up 20% of BandwidthThis tip made the rounds with people believing that Microsoft always allocates 20% of your bandwidth for Windows Update. According to the instructions, you were supposed to disable QoS in order to free up bandwidth. Unfortunately this tip was not only wrong, but disabling QoS will cause problems with applications that rely on it, like some streaming media or VoIP applications. Rather than taking my word for it, you can read the official Microsoft response: "There have been claims in various published technical articles and newsgroup postings that Windows XP always reserves 20 percent of the available bandwidth for QoS. These claims are incorrect... One hundred percent of the network bandwidth is available to be shared by all programs unless a program specifically requests priority bandwidth." Make Vista Use Multiple Cores to Speed Up Boot Time
According to this tip, you were supposed to use MS Config to modify the "Number of processors" drop-down on the Boot tab. The problem is that this setting is only used for troubleshooting and debugging, to be able to determine if there is a problem with a single processor, or for a programmer to test their code against a single core while running on a multi-core system. Windows will use all your processors by default without this setting. Clearing Out Windows Prefetch for Faster StartupThe Prefetch feature in Windows XP caches parts of applications that you frequently use and tries to optimize the loading process to speed up application start time, so when a number of sites started suggesting that you clean it out regularly to speed up boot time it seemed like good advice... but sadly that's not the case, as pointed out by many Lifehacker commenters. The Prefetch feature is actually used as a sort of index, to tell Windows which parts of an application should be loaded into memory in which order to speed up application load time, but Windows doesn't use the information unless it's actually starting an application. There's also a limit of 128 files that can be stored in the prefetch folder at any point, and Windows cleans out the folder automatically, removing information for applications that haven't been run as frequently. Not only that, but a well-written defrag utility will use the prefetch information to optimize the position of the files on the disk, speeding up access even further. Windows expert Ed Bott explains it:
Cleaning the Registry Improves Performance
This isn't to say they are completely useless, of course. I'd still recommend cleaning the registry when you are trying to troubleshoot a problem caused by uninstalling buggy software that leaves entries behind, but even then you should be very careful to use a reputable application like previously mentioned CCleaner and review the entries before deleting anything. Ed Bott weighs in with
a stronger opinion: I?d go a step further: Don?t run registry cleaner programs, period. I won?t go so far as to call them snake oil, but what possible performance benefits can you get from ?cleaning up? unneeded registry entries and eliminating a few stray DLL files? Clear Memory by Processing Idle TasksBy this point you should be starting to get the picture... if something sounds too good to be true, it likely is. This well-traveled tip usually claims that you can create an "undocumented" shortcut to Rundll32.exe advapi32.dll,ProcessIdleTasks that will clear out memory by processing all of the idle tasks wasting memory in the background. What's the problem? Those idle tasks aren't actually waiting in the background... what you are effectively doing is telling the computer that you've walked away so it can now do other processing while you are idle. Except you aren't. The real purpose of this functionality is to finish all processing before running benchmarks to ensure consistent times, and according to the Microsoft documentation there's a whole different story:
Read more at The Life of a Techno-Guru blog in a post called Response to Digg Article Claiming to Free up Memory. Clean, Defrag and Boost Your RAM With SnakeOil Memory Optimizer
Both of the techniques make it appear that you've suddenly freed up memory, when in reality all you've done is trade in your blazing fast RAM for a much slower hard drive. Once you have to switch back to an application that has been moved to the pagefile, it'll be so slow you'll be likely to go all Office Space on your machine. Windows expert Mark Russinovich agrees:
Disabling Shadow Copy/System Restore Improves Performance
The reality is that System Restore only actually kicks in when you are installing updates or applications, or at pre-scheduled times in the day, and the automatic checkpoints will only happen when your computer is not being used. These checkpoints allow you to easily roll back your system to a pre-crash state, and I can tell you from experience that System Restore is a critical feature when your Vista machine has problems, allowing you to easily get back to a working state. Instead of disabling System Restore to free up space, Ed Bott suggests that you simply use Disk Cleanup to remove all but the most recent restore point. (Under the More Options tab, you'll find a Clean up button). Enable SuperFetch in Windows XP
The good news is that this tip is one of the few that will not harm your system in any way, as long as you don't break something while editing the registry. If you insist on using it, I won't complain. If you want some proof, you can use the strings.exe utility to see that "superfetch" doesn't exist anywhere in the XP kernel, or you can believe Ed Bott and Mark Russinovich, who have already debunked this myth. Disabling Services to Speed Up the ComputerPerhaps the most common myth is
the advice to disable all services that you aren't using. I realize this
will generate some controversy, so let me clarify: Disabling non-essential
services that are NOT part of Windows will sometimes yield a performance
gain if you have identified those services as causing a problem. You can
identify or disable those services by opening msconfig.exe and checking the
box for "Hide all Microsoft services" on the Services tab: The problem with disabling services is that your devices will often not work once you do: for instance, I disabled the "Unknown" dlbt_device service in the list above, and could no longer print to my Dell printer... disabling the VMware services made VMware unable to run, and so forth. You should be even more careful to not disable built-in Microsoft services in Windows, except for a select few under certain circumstances:
If someone tries to talk you into disabling a bunch of other services, ask them what you stand to gain. I?ll bet they can?t tell you. Editor: Readers should note that a recent Windows Vista tweaking guide, offered for download by Microsoft, does suggest disabling unneeded services. When it comes to performance tweaking, a very large amount of testing is required each and every time you make a change. The better option is to simply install more RAM and clean up your PC if you are having performance problems, and perhaps demand a little more proof before applying secret hacks. The How-To Geek is a tech writer and geek enthusiast who loves to tinker with hidden settings that actually work. More of his tips and tweaks can be found daily at Howtogeek.com. |
Tue, 05 Aug 2008 |
||||
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||