Does seeing "EnablePrefetcher"=dword:5 make you go like this ->
?When someone happens to mention setting AdditionalCriticalWorkerThreads to 100, do you have an urge to beat that person about the head yelling "THE MAXIMUM IS SIXTEEN YOU $@%#& MORON!"?
If this describes you, then you should really seek the attention of a certified psychologist.
But for anyone who hates registry myths, regardless of sanity, this thread is for you.
Registry Myths #1: IoPageLockLimit
sample misinformation:
QUOTE
This tweak boosts the Input/Output performance of your computer when it is doing a large amount of file transfers and other similar operations. This tweak won't do much of anything for a system without a significant amount of RAM (if you don't have more than 128 MB, don't even bother), but systems with more than 128 MB of RAM will generally find a performance boost by setting this to between 8 and 16 MB. The default is 0.5 MB, or 512 KB. This setting requires a value in bytes, so multiply the desired number of megabytes * 1024 * 1024. That's X * 1048576 (where X is the number, in megabytes). Test out several settings and keep the one which seems to work best for your system.
[Source: http://www.subvers.com/technobabble/html/tweaking.htm]
[Source: http://www.subvers.com/technobabble/html/tweaking.htm]
QUOTE
Configure the amount of memory that can be locked for I/O Post Comment
There is a limit for how much memory the system can lock for I/O (Input/Output) operations. Increasing the limit might benefit applications or drivers, which are highly dependent on highspeed network or harddisk access, as it will allow a larger amount of outstanding I/O.
This DWORD value specifies how much memory (in bytes) that can be locked for I/O operations:
[HKEY_LOCAL_MACHINE \System \CurrentControlSet \Control \Session Manager \Memory Management]IoPageLockLimit=0 (0 = Calculated at boot, Default = 0)
One can use the following chart for finding a value, though the best value is found by testing:
Total RAM(MByte) IoPageLockLimit(Hex) Max Value
64 0 Total RAM minus 7 MByte
64-200 800000 Total RAM minus 16 MByte
256-500 1000000 Total RAM minus 16 MByte
512+ 2000000 Total RAM minus 64 MByte
[Source: http://snakefoot.fateback.com/tweak/winnt/tweak.html#IOLOCK]
There is a limit for how much memory the system can lock for I/O (Input/Output) operations. Increasing the limit might benefit applications or drivers, which are highly dependent on highspeed network or harddisk access, as it will allow a larger amount of outstanding I/O.
This DWORD value specifies how much memory (in bytes) that can be locked for I/O operations:
[HKEY_LOCAL_MACHINE \System \CurrentControlSet \Control \Session Manager \Memory Management]IoPageLockLimit=0 (0 = Calculated at boot, Default = 0)
One can use the following chart for finding a value, though the best value is found by testing:
Total RAM(MByte) IoPageLockLimit(Hex) Max Value
64 0 Total RAM minus 7 MByte
64-200 800000 Total RAM minus 16 MByte
256-500 1000000 Total RAM minus 16 MByte
512+ 2000000 Total RAM minus 64 MByte
[Source: http://snakefoot.fateback.com/tweak/winnt/tweak.html#IOLOCK]
Anyone who has done any kind of registry tweaking has seen IoPageLockLimit. It's all over the net, from Winguides, to Pure Performance, to Kelly's Korner, to TechSpot, to even Ars Technica. It's in every tweaking program you've ever used and most you haven't. Even the hallowed Expert's Exchange endorses this registry entry, although no one seems to be able to agree on exactly what format the values are supposed to be in.
What if I told you that this registry entry does absolutely jack? In fact, it isn't even read by the OS, or any other function of the system.
Wait a minute, you say. If this registry entry is bunk, then explain this:
http://www.microsoft.com/windows2000/techi...entry/29932.asp
Big Daddy MS itself says this thing works. So what do you say to that, Mr. Fancypants?
I say yes, you're right, it's true. In Windows 2000 RTM it was a real and valid setting. However, starting with W2000 SP1 and continuing with every subsequent release from 2K to XP to Server 2003 and everything in between, there is no reference to this registry value. In fact, in Windows XP and Windows Server 2003, the I/O Page Lock Limit is locked to 64mb.
QUOTE
Windows 2000 Power Users
Volume 3, Number 16
December 5, 2003
Killing a Myth or Three (or, Getting My Foot Out of My Mouth)
I was going to start talking about Longhorn this issue, but something more important (to me) has come up. Every now and then I realize that I have been inadvertently responsible for spreading a piece of information that turns out to be simply not true. When that happens, the only thing to do is sit down and make a meal out of my own words, sometimes salted liberally with crow.
Take, for instance, a certain Registry hack that is bandied around as being a performance-enhancer in both Windows 2000 and XP. This is the IoPageLockLimit hack, which (according to its proponents) allows you to change the amount of memory locked for exclusive access by the kernel. Setting this to a bigger value should lock more memory at once and in theory enhance performance. And indeed, it does do this -- but only in an RTM Windows 2000 machine. It does absolutely nothing in Windows 2000 Service Pack 1 and up, and absolutely nothing in Windows XP. This makes it effectively useless, since I know of no one in their right minds who runs Windows 2000 RTM on a production machine at this point in time.
How did I fall into this trap? Easy -- I tested it on a machine with Win2K RTM installed! It sure seemed to have an effect there, although not always a healthy one, and when I wrote about it I noted that this was a your-mileage-may-vary situation, and that seemed to be the end of it. The sheer amount of stuff out there to write about is intimidating, and I didn't want to spend weeks and weeks beating on the same issues until all but the most stalwart had fled or given up in boredom. I was applying a fair level of skepticism to the subject, but evidently it wasn't enough. (You can read what I wrote here: http://www.thegline.com/win2k/issues/2002/22.html)
One of the people who woke me up to how this whole IoPageLockLimit thing was a giant shill was Jamie Hanrahan of Kernel Mode Systems (http://www.cmkrnl.com). He had proof, he claimed, that the setting was absolutely worthless as of Win2K SP1 and up. He had run a string analysis on NTOSKRNL.EXE, looking for the actual Registry entry itself to see if it was being referenced by the kernel, and what he found was eye-opening. The RTM kernel references IoPageLockLimit. The SP1 kernel does not. Neither do any subsequent editions of the kernel; neither does the XP kernel in any of its incarnations. To double-check, he ran SysInternals' RegMon utility to determine if anything was, in fact, accessing that Registry entry at all, and the answer seemed to be a resounding no. There seem to be no references to the entry in any other system components, either. (I ran GREP on pretty much the whole Windows directory and came up empty.)
So why did some people report performance gains when they did this? There are plenty of explanations that have more to do with psychology and behavior than anything else. One of them is simple enough: that while making this tweak they did other things that may have legitimately affected their system performance (like do a defrag or clean up their boot acceleration cache, if they used XP). The other is nothing more than the placebo effect, where people perceive changes that simply aren't there, without having hard numbers to back it up. (Guilty!)
Now, the Ars Technica site, themselves no slouches, have reprinted the trick (at http://www.arstechnica.com/tweak/nt/IO-1.html), along with hard numbers to back it up -- but only under NT 4.0, not Windows 2000! Evidently a lot of people (myself included) have been mindlessly following the bandwagon that NT 4.0 = 2000 when it serves them and NT 4.0 <> 2000 when it does not.
On the one hand, this is bad news, because it means I've been inadvertently been spreading things which seemed to be facts, but which simply no longer have any truth to them, and haven't for some time. On the other hand, there is some good news here -- it means that the amount of stuff that needs to be tweaked in a Win2K or WinXP system is that much smaller, and that the system has apparently been made that much more self-regulating lately. I don't know about you, but I didn't particularly relish the thought of taking days to try and tweak my cache settings. (How does that song go? "Always ... look on ... the bri-ight side of life...") If it means I have to go and make a mess of retractions, then so be it. I'd rather do that than continue to knowingly be wrong.
I think an old adage is worth trotting out: Believe half of what you see and none of what you hear.
[Source: http://www.thegline.com/win2k/issues/2003/16.html#1]
Volume 3, Number 16
December 5, 2003
Killing a Myth or Three (or, Getting My Foot Out of My Mouth)
I was going to start talking about Longhorn this issue, but something more important (to me) has come up. Every now and then I realize that I have been inadvertently responsible for spreading a piece of information that turns out to be simply not true. When that happens, the only thing to do is sit down and make a meal out of my own words, sometimes salted liberally with crow.
Take, for instance, a certain Registry hack that is bandied around as being a performance-enhancer in both Windows 2000 and XP. This is the IoPageLockLimit hack, which (according to its proponents) allows you to change the amount of memory locked for exclusive access by the kernel. Setting this to a bigger value should lock more memory at once and in theory enhance performance. And indeed, it does do this -- but only in an RTM Windows 2000 machine. It does absolutely nothing in Windows 2000 Service Pack 1 and up, and absolutely nothing in Windows XP. This makes it effectively useless, since I know of no one in their right minds who runs Windows 2000 RTM on a production machine at this point in time.
How did I fall into this trap? Easy -- I tested it on a machine with Win2K RTM installed! It sure seemed to have an effect there, although not always a healthy one, and when I wrote about it I noted that this was a your-mileage-may-vary situation, and that seemed to be the end of it. The sheer amount of stuff out there to write about is intimidating, and I didn't want to spend weeks and weeks beating on the same issues until all but the most stalwart had fled or given up in boredom. I was applying a fair level of skepticism to the subject, but evidently it wasn't enough. (You can read what I wrote here: http://www.thegline.com/win2k/issues/2002/22.html)
One of the people who woke me up to how this whole IoPageLockLimit thing was a giant shill was Jamie Hanrahan of Kernel Mode Systems (http://www.cmkrnl.com). He had proof, he claimed, that the setting was absolutely worthless as of Win2K SP1 and up. He had run a string analysis on NTOSKRNL.EXE, looking for the actual Registry entry itself to see if it was being referenced by the kernel, and what he found was eye-opening. The RTM kernel references IoPageLockLimit. The SP1 kernel does not. Neither do any subsequent editions of the kernel; neither does the XP kernel in any of its incarnations. To double-check, he ran SysInternals' RegMon utility to determine if anything was, in fact, accessing that Registry entry at all, and the answer seemed to be a resounding no. There seem to be no references to the entry in any other system components, either. (I ran GREP on pretty much the whole Windows directory and came up empty.)
So why did some people report performance gains when they did this? There are plenty of explanations that have more to do with psychology and behavior than anything else. One of them is simple enough: that while making this tweak they did other things that may have legitimately affected their system performance (like do a defrag or clean up their boot acceleration cache, if they used XP). The other is nothing more than the placebo effect, where people perceive changes that simply aren't there, without having hard numbers to back it up. (Guilty!)
Now, the Ars Technica site, themselves no slouches, have reprinted the trick (at http://www.arstechnica.com/tweak/nt/IO-1.html), along with hard numbers to back it up -- but only under NT 4.0, not Windows 2000! Evidently a lot of people (myself included) have been mindlessly following the bandwagon that NT 4.0 = 2000 when it serves them and NT 4.0 <> 2000 when it does not.
On the one hand, this is bad news, because it means I've been inadvertently been spreading things which seemed to be facts, but which simply no longer have any truth to them, and haven't for some time. On the other hand, there is some good news here -- it means that the amount of stuff that needs to be tweaked in a Win2K or WinXP system is that much smaller, and that the system has apparently been made that much more self-regulating lately. I don't know about you, but I didn't particularly relish the thought of taking days to try and tweak my cache settings. (How does that song go? "Always ... look on ... the bri-ight side of life...") If it means I have to go and make a mess of retractions, then so be it. I'd rather do that than continue to knowingly be wrong.
I think an old adage is worth trotting out: Believe half of what you see and none of what you hear.
[Source: http://www.thegline.com/win2k/issues/2003/16.html#1]
Full credit for discovering this registry myth goes to Windows 2000 Power Users (www.Win2KPowerUsers.com).
. If you mean does it physically lock pages in RAM for only the I/O subsystem to use, yes. If it provides marked improvement over the defaults the box uses otherwise, probably not in most cases.
hell, wo wrote that piece of software? can we give him a call? 