View Full Version : Let Win2k/XP use your L2 cache properly
Dehcbad25
June 24th, 2003, 03:48 AM
For users of Windows 2000 or XP you actually have to tell the OS what size L2 cache your processor has otherwise it won't be used properly! Luckily it's fairly easy to fix.
Click on the Start button then go to run. From there type REGEDIT and press the "Ok" button. After it opens the Registry Editor follow this path. hkey_local_machine, System, CurrentControlSet, Control, Session Manager, Memory Management
Once you're in the Memory Management folder look for the DWORD value
secondleveldatacache.
Right click on that and go to modify. Very important you have to change the Base from Hexidecimal to Decimal before modifying the values. After that's done just punch in your L2 cache size so if you're using an AthlonXP since the CPU has 256KB L2 Cache you enter 256. For Duron's enter 64 and for P4 Northwood's enter 512.
After that's done you should notice your programs now have quite a bit more zip and the system is less sluggish because Windows now knows how to use your L2 cache properly.
Note: You can look your CPU L2 Cache in Chipgeek (http://www.geek.com/procspec/procspec.htm)
Also it is a great site to look at techinical specifications for any CPU :D
Thor
June 24th, 2003, 04:17 AM
Nice tip/tweak, Dehcbad25. Thanks
SupaStar
June 24th, 2003, 06:06 AM
Thanks...Just confirmed that mine's set correctly.
BTW - Nice link to Chipgeek. Very useful site :)
lynchknot
June 24th, 2003, 06:09 AM
thanks D mine was set at 0
Conan
June 24th, 2003, 06:15 AM
Couldn't find any entry for "secondleveldatacache".
SupaStar
June 24th, 2003, 07:40 AM
Sure you do...it's right here: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management :D
Conan
June 24th, 2003, 08:06 AM
When I enabled the tweak in Tweak XP it showed up. Had to edit it though since it changed the value to 512 instead of the proper 256.
Big Booger
June 24th, 2003, 09:40 AM
Nice tip. So what would the value be if it were 0? Does it have some sort of default or does XP really think you have 0 bytes of L2 cache?
SupaStar
June 24th, 2003, 09:49 AM
Originally posted by Big Booger
Nice tip. So what would the value be if it were 0? Does it have some sort of default or does XP really think you have 0 bytes of L2 cache?
Not sure if XP has a default value. I have had (not now) TweakXP installed before so it's possible that it was already set from that.
Maybe 0 is a default value - kind of like a "let windows manage my level 2 cache" :p
Dehcbad25
June 24th, 2003, 19:11 PM
sorry, I forgot one little detail. As BB pointedd out, what happens when it is "0"?:p
My bad
If it is "0" make sure you have the proper L2 value and enter it in decimal value. By default it will be Hexadecimal, so make sure you are in Decimal.
SupaStart posted a perfect picture for it. I don't recomend using a higher value than your actual L2 because you risk to lose data.
0 unfortunately means that XP won't use L2 cash.
This will happen when your CPU is not recognized, so when all updates are installed you could have the right value.
Also it is usual for AMD. Take it as you like (MS likes Intel) ;)
efc
June 24th, 2003, 20:16 PM
Nice tip. Mine was also set at 0.
cash_site
June 27th, 2003, 16:42 PM
Originally posted by SupaStar
Not sure if XP has a default value. I have had (not now) TweakXP installed before so it's possible that it was already set from that.
Maybe 0 is a default value - kind of like a "let windows manage my level 2 cache" :p
I think XP default is zero, cos before installed tweakxp it was zero, then after install went to 64 for my duron.
Dehcbad25
June 28th, 2003, 05:43 AM
As I said it is ) if it doesn't recognize the code for the CPU. This happens when your CPU is newer than the release of the OS, or relatively new. XP uses the CPUID to get the value of the L2 Cash, so when it doesn't know how much there is, it preffers not to use it, in favor of making the system unstable.
Lets say your value is 512 instead of 256, then the OS could crash, though with XP it tries to put the extra 256 in RAM. The drawnback is that the CPU won't recognize those extra 256, so they will get lost when you shutdown. Eventually, you coudl corrupt date, or the OS itself
zipp51
June 28th, 2003, 10:53 AM
In the modification box it is set at 200 for hexidecimal value and when I choose decimal it changes it's value to 512.I assume the 2 values are equal because if I punch in other values in the decimal form it also changes the value in hexidecimal.Is hexidecimal the default for windows to comunicate with the hardware?
Dehcbad25
June 28th, 2003, 20:34 PM
The default value for that type of Key is hexdecimal.
And yes, 200 hex means 512 decimal, and 100 hex means 256 :D
|
|