Anthony Cogan
tco...@one-stop.com
Which version of NT are you running? If you are running Server as a workstation,
you need to change the following registry setting to adjust the way dynamic
caching is implemented: (use regedt32)
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management\LargeSystemCache = 1 should be set to 0.
Shut down NTS and restart. I would even check this setting in NTWS, even though
it is supposed to be set to zero on workstation by default.
Some explanation: What this does if set "true" (i.e. 1) is tilt memory
allocation priority towards the dynamic file system cache and away from process
memory. This usually works well on Servers with large amounts of memory where
file I/O is just as, or more, important than running applications. In systems
where applications need lots of memory, memory is (relatively) limited, and file
I/O is causing excessive demand based paging to virtual memory due to cache
growth, this setting should be returned to zero. This will place memory
allocation to the dynamic cache lower than allocation to processes, and prevent
the thrashing you are seeing.
R/
James C. Owens
j...@norfolk.infi.net, jco...@exis.net,
running Windows NT 4.0 Server (Build 1381).
Pentium 133, 64 MB RAM, 2x2 GB 8 ms F-W SCSI-2 HD's.