Easy Way to Adjust Large System Cache
Normally, the tweak I've seen asks you to go into
HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management and change the value to either 0 or 1 to the adjustment the LargeSystemCache.
However, in Windows XP, all you have to do is:
• Right-click My Computer.
• Select Properties.
• Click Advanced.
• Choose Performance.
• Click Advanced again.
• Select either Programs or System Cache under Memory Usage.
Programs = 0 for the registry tweak equivalent
System Cache = 1 for the registry tweak equivalent
• On NT Server (in this case XP), the Large System Cache option is enabled, but disabled on Workstation. The two different settings effect how the cache manager allocates free memory. If the Large Cache option is on, the manager marks all the free memory, which isn't being used by the system and/or applications, as freely available for disk caching.
• On the flip-side (with a small cache), the manager instead only sets aside 4MB of memory for disk caching in an attempt to accelerate the launch of applications. Or in a more technical approach, if enabled the system will favor system-cache working sets over process working sets (with a working set basically being the memory used by components of a process).
Normally, the tweak I've seen asks you to go into
HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management and change the value to either 0 or 1 to the adjustment the LargeSystemCache.
However, in Windows XP, all you have to do is:
• Right-click My Computer.
• Select Properties.
• Click Advanced.
• Choose Performance.
• Click Advanced again.
• Select either Programs or System Cache under Memory Usage.
Programs = 0 for the registry tweak equivalent
System Cache = 1 for the registry tweak equivalent
• On NT Server (in this case XP), the Large System Cache option is enabled, but disabled on Workstation. The two different settings effect how the cache manager allocates free memory. If the Large Cache option is on, the manager marks all the free memory, which isn't being used by the system and/or applications, as freely available for disk caching.
• On the flip-side (with a small cache), the manager instead only sets aside 4MB of memory for disk caching in an attempt to accelerate the launch of applications. Or in a more technical approach, if enabled the system will favor system-cache working sets over process working sets (with a working set basically being the memory used by components of a process).
1 comments:
WARNING!
Microsoft has made it quite clear, this setting is only for systems used primarily as file servers, and then only in specific cases. For workstation or gaming use this will almost always be a bad idea. It basically tells Windows that file caching has priority over memory for applications. This can seriously impair application performance.
Or worse. This setting is potentially dangerous with some common hardware configurations. Some users have reported severe performance hits, system instability, and data corruption. It is deadly with some common video cards and other devices. Some users have been forced to reinstall Windows to restore operation.
Anyone contemplating this setting must thoroughly invertigate the issues and possible risks.
YOU HAVE BEEN WARNED.
References:
http://support.microsoft.com/kb/895932
Larry Miller
Microsoft MCSA
Post a Comment