Memory tweak question

  • Thread starter Thread starter Steve o.o.o.o.o
  • Start date Start date
S

Steve o.o.o.o.o

Does anybody have any info about these tweaks? I have only found
positive info on the web about this. But i'm looking for any negative
aspects to implementing these.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Memory
Management]
"DisablePagingExecutive"=dword:00000001
"LargeSystemCache"=dword:00000001
 
DisablePagingExecutive
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

Data type Range Default value
REG_DWORD 0 | 1 0

Description
Specifies whether user-mode and kernel-mode drivers and kernel-mode system code can be paged to disk when not in use.

Value Meaning
0 Drivers and the kernel must remain in physical memory.
1 Drivers and the kernel can be paged to disk as needed.

LargeSystemCache
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

Data type Range Default value
REG_DWORD 0 | 1 Windows 2000 Professional: 0
Windows 2000 Server: 1

Description
Determines whether the system maintains a standard size or a large size file system cache, and influences how often the system writes changed pages to disk.

Increasing the size of the file system cache generally improves server performance, but it reduces the physical memory space available to applications and services. Similarly, writing system data less frequently minimizes use of the disk subsystem, but the changed pages occupy memory that might otherwise be used by applications.

Value Meaning
0 Establishes a standard size file system cache of approximately 8 MB. The system allows changed pages to remain in physical memory until the number of available pages drops to approximately 1000. This setting is recommended for servers running applications that do their own memory caching, such as Microsoft SQL Server, and for applications that perform best with ample memory, such as Internet Information Services.
1 Establishes a large system cache working set that can expand to physical memory, minus 4 MB, if needed. The system allows changed pages to remain in physical memory until the number of available pages drops to approximately 250. This setting is recommended for most computers running Windows 2000 Server on large networks.

Caution

Setting this value to 1 can have an impact on the performance of any services that run on the server. A value of 1 should be used only if the server is used exclusively as a file server.
 
To explain what David posted, ask yourself one question.

Do want the OS to run the OS or your applications?
 
Thanks. That one little sentence really sums it up for me (Do want the
OS to run the OS or your applications?). But Davids post is the techno
jargon I need to throw at somebody to get them off my back about this
"tweak". In this environment with some many applications (500 diff apps
for less then 1500 users) I think I have my answer.

Thanks again,
-Steve
 
Steve o.o.o.o.o rambled on in microsoft.public.windowsxp.customize:
Does anybody have any info about these tweaks? I have only found
positive info on the web about this. But i'm looking for any negative
aspects to implementing these.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Memory
Management]
"DisablePagingExecutive"=dword:00000001
"LargeSystemCache"=dword:00000001

I've tried them and I have a athlon xp and 1 gig of ram and didn't see any
improvement
 
Also Microsoft recommends a page file on two drives if you have 2 I did this
and saw a great performance boost.
 
Back
Top